From: Michael Heerdegen <michael_heerdegen@web.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error with tramp-archive-autoload-file-name-handler
Date: Mon, 28 Mar 2022 04:20:03 +0200 [thread overview]
Message-ID: <87fsn2q0mk.fsf@web.de> (raw)
In-Reply-To: <87y20vg5gu.fsf@gmx.de> (Michael Albinus's message of "Sun, 27 Mar 2022 10:33:21 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> I cannot reproduce. The following works fine:
>
> $ emacs -Q -l tramp --eval "(add-to-list 'file-name-handler-alist (cons (tramp-archive-autoload-file-name-regexp) #'tramp-archive-autoload-file-name-handler))" --eval '(file-directory-p "/home/albinus/tmp/out.tar.xz/")'
You missed the TWICE part in my last message. Just eval the above
twice:
$ emacs -Q -l tramp --eval "(add-to-list 'file-name-handler-alist (cons (tramp-archive-autoload-file-name-regexp) #'tramp-archive-autoload-file-name-handler))" --eval '(file-directory-p "/home/albinus/tmp/out.tar.xz/")'\
--eval "(add-to-list 'file-name-handler-alist (cons (tramp-archive-autoload-file-name-regexp) #'tramp-archive-autoload-file-name-handler))" --eval '(file-directory-p "/home/albinus/tmp/out.tar.xz/")'
Sorry, but that's the best recipe I can offer. And I guess something
like this is actually happening. AFAIU, Tramp can call
`tramp-register-archive-file-name-handler' several times - see
tramp-archive.el line 394:
```
;; In older Emacsen (prior 27.1), the autoload above does not exist.
;; So we call it again; it doesn't hurt.
(tramp-register-archive-file-name-handler)
```
and my interpretation is that at least in my case that does hurt.
But let's first see if you can reproduce the recipe now, and interpret
the result later...
Thanks,
Michael.
next prev parent reply other threads:[~2022-03-28 2:20 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 [this message]
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
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=87fsn2q0mk.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=michael.albinus@gmx.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).