From: Michael Albinus <michael.albinus@gmx.de>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: 13636@debbugs.gnu.org
Subject: bug#13636: 24.3.50; tramp+ftp broken
Date: Wed, 06 Feb 2013 17:14:50 +0100 [thread overview]
Message-ID: <8738x9a079.fsf@gmx.de> (raw)
In-Reply-To: <871ucttoxi.fsf@gmail.com> (Thierry Volpiatto's message of "Wed, 06 Feb 2013 16:58:01 +0100")
Thierry Volpiatto <thierry.volpiatto@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\b@\bA\"\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.
next prev parent reply other threads:[~2013-02-06 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 13:35 bug#13636: 24.3.50; tramp+ftp broken Thierry Volpiatto
2013-02-06 14:26 ` Michael Albinus
2013-02-06 14:42 ` Thierry Volpiatto
2013-02-06 14:54 ` Thierry Volpiatto
2013-02-06 15:39 ` Michael Albinus
2013-02-06 15:58 ` Thierry Volpiatto
2013-02-06 16:14 ` Michael Albinus [this message]
2013-02-06 16:47 ` Thierry Volpiatto
2013-02-06 18:36 ` Eli Zaretskii
2013-02-06 19:23 ` Thierry Volpiatto
2013-02-06 18:59 ` Michael Albinus
2013-02-06 19:21 ` Thierry Volpiatto
2013-02-06 20:15 ` Michael Albinus
2013-02-06 21:02 ` Thierry Volpiatto
2013-02-07 8:56 ` Michael Albinus
2013-02-08 12:36 ` Thierry Volpiatto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738x9a079.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=13636@debbugs.gnu.org \
--cc=thierry.volpiatto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).