From: Michael Heerdegen <michael_heerdegen@web.de>
To: Felix Dietrich <felix.dietrich@sperrhaken.name>
Cc: help-gnu-emacs@gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: Re: Error with tramp-archive-autoload-file-name-handler
Date: Wed, 13 Apr 2022 04:03:09 +0200 [thread overview]
Message-ID: <877d7tg2oy.fsf@web.de> (raw)
In-Reply-To: <87fsmog4om.fsf@sperrhaken.name> (Felix Dietrich's message of "Thu, 07 Apr 2022 19:54:17 +0200")
Felix Dietrich <felix.dietrich@sperrhaken.name> writes:
> >> Perhaps you could provide a ChangeLog-style commit message?
>
> Thanks for taking care of fixing the style of my commit message. :)
And thank you for your help and your patch!
> an error message “Recursive load” (no hang due to an infinite loop
> though). Do you remember why using ‘defalias’ here causes an infinite
> recursion?
I think the debugger should be able to catch that one, and with Elisp
sources loaded the backtrace should provide enough information to find
the reason.
Michael.
next prev parent reply other threads:[~2022-04-13 2:03 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
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 [this message]
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=877d7tg2oy.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=felix.dietrich@sperrhaken.name \
--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).