[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tramp (2.0.0); No such file or directory error

From: Kai Großjohann
Subject: Re: tramp (2.0.0); No such file or directory error
Date: Thu, 21 Nov 2002 18:37:19 +0100
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu)

Matt Dickerson <address@hidden> writes:

> I like to use tramp to Dired remote directories. Here is my backtrace:
> ,----[ *Backtrace* ]
> | Debugger entered--Lisp error: (file-error "Reading directory" "no such file 
> or directory" "/address@hidden")
> |   access-file("/address@hidden" "Reading directory")
> |   apply(access-file ("/address@hidden" "Reading directory"))
> |   tramp-completion-run-real-handler(access-file ("/address@hidden" "Reading 
> directory"))
> |   tramp-completion-file-name-handler(access-file "/address@hidden" "Reading 
> directory")
> |   access-file("/address@hidden" "Reading directory")
> |   insert-directory("/address@hidden" "-al" t nil)
> |   apply(insert-directory ("/address@hidden" "-al" t nil))
> |   tramp-completion-run-real-handler(insert-directory ("/address@hidden" 
> "-al" t nil))
> |   tramp-completion-file-name-handler(insert-directory "/address@hidden" 
> "-al" t nil)
> |   insert-directory("/address@hidden" "-al" t nil)
> |   dired-insert-directory("/address@hidden" "-al" t)
> |   dired-readin-insert("/address@hidden")
> |   dired-readin("/address@hidden" #<buffer address@hidden>)
> |   dired-internal-noselect("/address@hidden" nil)
> |   dired-noselect("/address@hidden" nil)
> |   dired("/address@hidden" nil)
> |   call-interactively(dired)
> `----
> Also curious and annoying when using almost any commands that require
> shell output, I also get part of my shell prompt inserted into
> buffers.  Could that be the problem?  Here's the output from Dired.
> First as listed in buffer-menu:
>  *  address@hidden  70 Dired by name /address@hidden

Maybe you could try Tramp 2.0.25 which I believe is the current

Secondly, your output indicates that the shell prompt is using ansi
color escape sequences.  This is too tough for Tramp to handle (Tramp
needs to grok the shell prompt).  Therefore, I propose that you
either change shell-prompt-pattern or tramp-shell-prompt-pattern to
match your shell prompt, or that you change the shell init files to
abstain from escape sequences if used from Tramp.

When Tramp invokes a shell, it sets $TERM to dumb (configurable via
tramp-terminal-type).  In the shell init files, you can check on that:

if [ x$TERM = xdumb ]; then
    # no fancy prompt

Tramp 2.0.25 uses a different filename format:


instead of


~/.signature is: umop ap!sdn    (Frank Nobis)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]