From: Michael Albinus <michael.albinus@gmx.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error with tramp-archive-autoload-file-name-handler
Date: Tue, 29 Mar 2022 09:30:31 +0200 [thread overview]
Message-ID: <87wngddxm0.fsf@gmx.de> (raw)
In-Reply-To: <87v8vx7gsz.fsf@web.de> (Michael Heerdegen's message of "Tue, 29 Mar 2022 02:17:48 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
Hi Michael.
> Here is a recipe for emacs -Q:
>
> M-:
>
> (dotimes (_ 2)
> (add-to-list 'file-name-handler-alist
> (cons (tramp-archive-autoload-file-name-regexp)
> #'tramp-archive-autoload-file-name-handler))
> (file-directory-p
> "/home/micha/software/emacs/test/lisp/net/tramp-archive-resources/foo.iso/"))
>
> RET
>
> gives me:
>
> Debugger entered--Lisp error: (error "Invalid handler in ‘file-name-handler-alist’")
> file-directory-p("/home/micha/software/emacs/test/lisp/net/tramp-arc...")
>
> Is that acceptable?
I'm afraid, this still doesn't raise any error here (tested with Emacs
git master and Emacs 27).
>> Anyway, I've pushed the appended patch to the repositories. It should fix
>> this problem, hopefully.
>
> Hmm - that actually fixes the real-life issue I see - but not the above
> recipe.
Of course! My patch avoids several calls of that add-to-list. So I guess
we can regard the problem as fixed, because the real-life issue is fixed
for you as well.
> Michael.
Thanks again for reporting, and for patient testing. Best regards, Michael.
next prev parent reply other threads:[~2022-03-29 7:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 23:44 Error with tramp-archive-autoload-file-name-handler Michael Heerdegen
2022-03-26 8:39 ` Michael Albinus
2022-03-26 19:01 ` Michael Heerdegen
2022-03-27 0:06 ` Michael Heerdegen
2022-03-27 8:33 ` Michael Albinus
2022-03-28 2:20 ` Michael Heerdegen
2022-03-28 6:08 ` Felix Dietrich
2022-03-28 10:25 ` Michael Albinus
2022-03-29 0:17 ` Michael Heerdegen
2022-03-29 7:30 ` Michael Albinus [this message]
2022-04-01 1:53 ` Michael Heerdegen
2022-04-02 12:00 ` Felix Dietrich
2022-04-02 17:00 ` Michael Albinus
2022-04-06 8:49 ` Felix Dietrich
2022-04-06 18:13 ` Michael Albinus
2022-04-07 10:14 ` Michael Albinus
2022-04-07 17:54 ` Felix Dietrich
2022-04-08 9:41 ` Michael Albinus
2022-04-13 2:03 ` Michael Heerdegen
2022-04-03 1:26 ` Michael Heerdegen
2022-04-03 15:57 ` Michael Albinus
2022-04-04 0:58 ` Michael Heerdegen
2022-04-04 7:40 ` Michael Albinus
2022-03-29 0:09 ` Michael Heerdegen
2022-03-27 8:16 ` Michael Albinus
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=87wngddxm0.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).