[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: command not found on remote server
From: |
Paul Jarc |
Subject: |
Re: command not found on remote server |
Date: |
Thu, 11 Dec 2008 16:34:47 -0500 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
Bob Proulx <bob@proulx.com> wrote:
> Also, using full paths is frowned upon.
You mean invoking /directory/some-command directly instead of
PATH=$PATH:/directory
some-command
? It depends on the situation. If you think some-command is in
/directory, but you want to allow for the possibility that it might be
somewhere else in $PATH, then augmenting $PATH and invoking
some-command by its basename is better. On the other hand, if you
know that the some-command you want is definitely in /directory, and
if there could be other versions of some-command elsewhere in $PATH
that are different from the one you want, then it's best to invoke
/directory/some-command by its full path.
paul