Re: Dealing with strange shell prompts

[Kai Großjohann]

lawrence mitchell <address@hidden> writes:

> Kai Grossjohann wrote:
>
>> It seems to happen more often now that Tramp doesn't grok a shell
>> prompt after "exec /bin/sh" on the remote end.  I wonder if "exec
>> /bin/sh" could be replaced by something else which can be expected to
>> work better?
>
>> How about, for example, the following?
>
>>     exec env PS1='$ ' /bin/sh
>
>> I think it works under csh-like shells as well as under Bourne-ish
>> shells.  (Note that this command is expected to start a Bourne-ish
>> shell, so at this point we're not allowed to assume that we are
>> talking to a Bourne-ish shell already.)
>
>> What about zsh?  Does it work there, too?
>
> It works for me under zsh 2.6-beta4, so I'd hope that it can be
> expected to work for more recent versions.  (The current release
> is 4.0.6).

Good.  I had been hoping it would work, after all zsh has the union
of the features of other shells, and then some.

>> And what about people with really unusual login shells, such as scsh
>> or this Plan9 thing?  Does Tramp currently work for them?  Will the
>> above command work there?
>
> The scsh isn't (as yet) really intended as an interactive shell
> (at least according to it's faq), so maybe you don't need to
> cater for it yet, however, a cursory glance at the Scheme manual
> suggests not.  You might want to try asking on
> comp.lang.scheme.scsh though.

OK.  So what about rc or rx or what is this Plan9 thing called?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)