From: Michael Albinus <michael.albinus@gmx.de>
To: 59194@debbugs.gnu.org
Cc: monnier@iro.umontreal.ca
Subject: bug#59194: 29.0.50; Tramp autoloads and ordering
Date: Fri, 18 Nov 2022 21:19:37 +0100 [thread overview]
Message-ID: <87cz9kvwva.fsf@gmx.de> (raw)
In-Reply-To: <jwvy1shd1px.fsf@iro.umontreal.ca> (Stefan Monnier via's message of "Fri, 11 Nov 2022 09:07:06 -0500")
Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
Hi Stefan,
> `tramp.el` has the following:
>
> ;;;###tramp-autoload
> (progn
> (defvar tramp--startup-hook nil
> "Forms to be executed at the end of tramp.el.")
> (put 'tramp--startup-hook 'tramp-suppress-trace t)
>
> (defmacro tramp--with-startup (&rest body)
> "Schedule BODY to be executed at the end of tramp.el."
> `(add-hook 'tramp--startup-hook (lambda () ,@body))))
>
> and then various other Tramp files have autoloaded forms like:
>
> ;;;###tramp-autoload
> (tramp--with-startup
> (add-to-list 'tramp-methods
> ...))
>
> The problem here is that the resulting `tramp-loaddefs.el` may or may
> not be valid depending on the order in which it gets filled, which is
> not something that's documented/guaranteed.
I'm aware of this. It was already reported on emacs-devel, see thread
starting with <87edvw7bjk.fsf@dataswamp.org>. In that case I've added
some variable declarations.
However, I don't know how to fix this in general.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2022-11-18 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 14:07 bug#59194: 29.0.50; Tramp autoloads and ordering Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-18 20:19 ` Michael Albinus [this message]
2022-11-18 21:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87cz9kvwva.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=59194@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).