Patrik Jonsson <[EMAIL PROTECTED]> writes:

> When trying to find a file on remote machines (I've tried linux FC6
> x86_64 and a SunOS 5.8 machine) using plink (v0.59) on Windows XP SP2,
> it fails when trying to determine which command to use to find out if
> a remote file exists. If I use Emacs 21.3 and tramp 2.0.48, I can
> connect fine.

It is still mysterious.

> # Setting shell prompt
> $ PS1='
> ///fba95ce3935b46bf9e4a12496466a798
> '; PS2=''; PS3=''
> $ echo ~root
> /root
> # Remote `/bin/sh' groks tilde expansion, good
> # Finding command to check if file exists
>
> The tramp output buffer (*tramp/plink machine*) is empty.

Reproducing the test locally (remote host runs Ubuntu, but it
shouldn't matter) shows:

# Setting shell prompt
$ PS1='
///69b9edf343eb473008d721d21a951698
'; PS2=''; PS3=''
$ echo ~root
/
# Remote `/bin/sh' groks tilde expansion, good
# Finding command to check if file exists
$ test -e / 2>/dev/null; echo tramp_exit_status $? 
tramp_exit_status 0
$ test -e /\ this\ file\ does\ not\ exist\  2>/dev/null; echo tramp_exit_status 
$? 
tramp_exit_status 1

...

And looking at the code, there is no reason that Tramp shouldn't raise
(and trace!)  the next command 'test -e / 2>/dev/null; echo
tramp_exit_status $?'

Hmm. Could you, please, restart Emacs with "emacs -q"? Then apply

(setq debug-on-error t
      debug-on-quit t)

and rerun the test please. It should give you a backtrace, which might
be helpful.

Best regards, Michael.



_______________________________________________
Tramp-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/tramp-devel

Reply via email to