Once one makes a tramp connection, any subsequent use of M-x shell is
altered, **even when invoked from innocent unrelated buffers**.
It now asks "Remote shell path: ...".
Well M-x shell's behavior is altered, but its docstring remains the
same.
So nobody can figure out how to just get it to act
積丹尼 Dan Jacobson writes:
Hi Dan,
> Once one makes a tramp connection, any subsequent use of M-x shell is
> altered, **even when invoked from innocent unrelated buffers**.
>
> It now asks "Remote shell path: ...".
This shall happen only for buffers which have a remote
default-directory. Please c
OK but if the user, while in a TRAMP window, decides to send an email,
this email window now is "infected" with the remote directory, and then
doing M-x shell there will also be "infected".
So maybe instead of looking at the default-directory, look at the buffer
name.
積丹尼 Dan Jacobson writes:
Hi Dan,
> OK but if the user, while in a TRAMP window, decides to send an email,
> this email window now is "infected" with the remote directory, and then
> doing M-x shell there will also be "infected".
>
> So maybe instead of looking at the default-directory, look at t
Well OK I'll do
(setq gnus-default-directory "~/")
(add-hook 'message-mode-hook ;news-reply-mode-hook
(function
(lambda ()
(setq default-directory "~/"
etc.
___
Tramp-devel mailing list
Tramp-devel@gnu.org
https://li