On 07 Nov 2000, Hannu Koivisto wrote:
> At least sudu method (sudm probably too) seems to assume that the
> shell (of the account one is sudoing to) is (ba)sh.
I think not.
> Thus, when I try to open, say, /r@sudu:root@localhost:/etc/passwd, I
> get (root's shell on the machine in question is zsh):
>
> set +o history
The only place that `history' occurs in tramp.el is in
tramp-open-connection-setup-interactive-shell, and near the beginning
of that function, Tramp sends the command "exec /bin/sh" to the remote
end (or whatever the value of tramp-remote-sh is set to for the given
method).
Hm. For the "sudu" method, tramp-remote-sh is set to "", the empty
string. Why?
Does it help to set this method parameter to "/bin/sh" instead?
> set: no such option: history
>
[senstation] set +o vi +o emacs
> set: no such option: vi
> set: no such option: emacs
>
[senstation] unset MAIL MAILCHECK MAILPATH 1>/dev/null 2>/dev/null
>
[senstation] PS1='
>
quote> /////
>
quote> '; PS2=''; PS3=''
>
> to *tramp/sudu root@localhost* buffer and
>
> Couldn't set remote shell prompt. \
> See buffer `*tramp/sudu root@localhost*' for details
It appears that there is also a problem with the EOL convention used
in that buffer. Arf.
kai
--
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing
