Hi Mike, thanks for the quick response. However it appears that eshell also suffers under the same behaviour, at least under my emacs 23.1.1.
After doing a C-h k TAB, which is bound to the comint-dynamic-complete function, it's possible the problem is there, or the functions it calls (in comint-dynamic-complete-functions). I'm keen on eliminating this issue, as I could (finally) completely ditch a regular terminal. -Matt On Mon, Feb 8, 2010 at 2:57 PM, Michael Albinus <[email protected]> wrote: > Matthew Curry <[email protected]> writes: > >> Hi all: > > Hi, > >> For instance, *Buffer List* shows this on spawning a remote shell with >> M-x shell: >> * *shell* 81 Shell:run /scp:soma:/home/e3/ >> >> I do a "cd /" (or just "cd", or "cd ~") and now *Buffer List* shows this: >> * *shell* 114 Shell:run / >> >> And from then on, tab autocomplete will look at the local machine's >> filesystem instead of the remote one. > > I would say it's the canonical behaviour. The shell mode does not know > of Tramp, it just sets the default directory to "/". And this is a local > file name. > >> So my question is a) is this a known problem and b) is there a way to >> make shell-mode respond to absolute paths more correctly? > > You are looking for eshell. This shell understands both native shell > commands, and kind of Elisp, for example syntax of remote file > names. See <http://www.gnu.org/software/tramp/#Remote-processes>, where > a sample eshell session is given. > > With Emacs 23.2, the eshell integration with Tramp will be even tighter, > because it understands then "su" and "sudo" commands on remote hosts, > and gives you respective file access. > >> Thanks, >> >> -Matt > > Best regards, Michael. > _______________________________________________ Tramp-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/tramp-devel
