GNU bug report logs - #13636
24.3.50; tramp+ftp broken

Previous Next

Package: emacs;

Reported by: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>

Date: Wed, 6 Feb 2013 13:38:01 UTC

Severity: normal

Found in version 24.3.50

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 13636 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Cc: 13636 <at> debbugs.gnu.org
Subject: Re: bug#13636: 24.3.50; tramp+ftp broken
Date: Wed, 06 Feb 2013 17:14:50 +0100
Thierry Volpiatto <thierry.volpiatto <at> gmail.com> writes:

Hi Thierry,

>> Tramp does not touches .netrc. ange-ftp shouldn't either, and there
>> haven't been recent changes I'm aware of.
>>
>> Hmm, unfortunately the most interesting part of the backtrace is byte
>> code. Could you, please, remove all *.elc from the lisp/ directory (and
>> subdirectories)? This might give us a better backtrace.
> Still have some byte-code, but more informative though.
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   signal(wrong-type-argument (stringp nil))
>   byte-code("\301@A\"\207" [err signal] 3)
>   ange-ftp-hook-function(file-remote-p "/ftp:mafreebox.freebox.fr:" nil nil)

Still not sufficient. I don't see where (stringp nil) is called.
"/ftp:mafreebox.freebox.fr:" is a string (obviously). The other
parameters of `file-remote-p' are optional, it is OK to be nil.

What happens, if you eval in your *scratch* buffer

(file-remote-p "/ftp:mafreebox.freebox.fr:" nil nil)

What happens, if you move your ~/.netrc away (temporarily)?

Best regards, Michael.




This bug report was last modified 12 years and 102 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.