unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Felix Dietrich <felix.dietrich@sperrhaken.name>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Error with tramp-archive-autoload-file-name-handler
Date: Sat, 02 Apr 2022 19:00:49 +0200	[thread overview]
Message-ID: <87v8vre7y6.fsf@gmx.de> (raw)
In-Reply-To: <877d873dak.fsf@sperrhaken.name> (Felix Dietrich's message of "Sat, 02 Apr 2022 14:00:51 +0200")

Felix Dietrich <felix.dietrich@sperrhaken.name> writes:

Hi Felix,

>> Anyway, when `tramp-archive-autoload-file-name-handler' is present after
>> tramp-archive-enabled has become nil, it is used and called but doesn't
>> handle the request (i.e. returns nil).  AFAIU, that was what I have been
>> seeing.
>
> Could the tramp error handler provide a more helpful error message in
> cases where it currently just returns nil?  Or are there limitations
> prohibiting this, for example in how Emacs processes file handlers?

tramp-archive-autoload-file-name-handler is just a temporary setting, it
doesn't get used after being replaced by tramp-archive-file-name-handler.

Since this bug is fixed now, I don't believe it is worthful to invest
more code there.

Best regards, Michael.



  reply	other threads:[~2022-04-02 17:00 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
2022-04-01  1:53                   ` Michael Heerdegen
2022-04-02 12:00                     ` Felix Dietrich
2022-04-02 17:00                       ` Michael Albinus [this message]
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=87v8vre7y6.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=felix.dietrich@sperrhaken.name \
    --cc=help-gnu-emacs@gnu.org \
    /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).