On Sat, 17 Mar 2001, Tom Roche wrote:
> On Fri, 16 Mar 2001, Tom Roche wrote:
>>> I get
>
>>>> *vc-diff*
>>>> /bin/ksh: cvs: not found
>
>>> How do I make ksh find cvs?
>
> Also, just wondering: why ksh? (A quick hand-waving explanation will
> probably suffice :-)
Well, Tramp works by sending commands to the remote end. It is
necessary to know which shell one is talking to for the commands to
come out right. For example, `PATH=foo; export PATH' will do no good
in a csh.
For this reason, the first thing Tramp does is to execute `exec
/bin/sh', that's pretty much guaranteed to exist, and it's a
Bourne-ish shell. Now, not all Bourne-ish shells grok tilde
expansion, but the user probably wants that.
So if /bin/sh does not do tilde expansion, Tramp looks in all the
directories listed in tramp-remote-path to see if it finds a ksh or
bash there. If so, that's executed.
> [EMAIL PROTECTED] 17 Mar 2001 13:32:21 +0100
>> Just add directories to tramp-remote-path and they will appear in
>> $PATH.
>
> Success! Which of course leads to further questions :-)
>
> It would be nice to be able to set 'tramp-remote-path on a
> per-server basis; presumably users will have different path-munging
> requirements on different servers. What's the "best way" to do this?
Why can't you just add all directories to this variable?
Does one host need directory a first and directory b second, and
another host needs it the other way round?
It is harmless to add nonexisting directories to this variable.
kai
--
Be indiscrete. Do it continuously.
