Kai Gro�johann writes:
> I now see that the order of operations might be wrong: first I say
> `exec /bin/sh', then I set up $PS1, then I search for a different
> shell, which might fire up /bin/ksh.
>
> I wonder if the ksh then uses the carefully set up $PS1?
I think I've spotted the problem. In rcp-find-shell the command 'exec
/bin/ksh' is sent and then shell-prompt-pattern is waited for. It
seems that PS1 is being exported from the initial /bin/sh. /bin/ksh is
starting but with a ///// style prompt which does not match
shell-prompt-pattern.
rcp.el works now if I change "exec " to "PS1='$ '; exec " in
rcp-find-shell.
I guess that rcp-open-connection-setup-interactive-shell will need the
same change.
--
Pete Forman | Disclaimer: This posting is originated by
Western Geophysical | myself and does not represent the opinion
[EMAIL PROTECTED] | of Baker Hughes or its divisions.
