all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52969@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#52969: Shortdoc "string" group leads to backtrace
Date: Mon, 03 Jan 2022 16:19:53 -0500	[thread overview]
Message-ID: <jwvr19ott7n.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <jwv8rvwv8m9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 03 Jan 2022 16:05:12 -0500")

> As for disadvantages to n°3, I remember trying it out some months ago but
> I can't remember why nor can I remember why I haven't kept this change
> in my local hacks.  Sorry.

I seem to remember that one of the motivations for trying it out had to
do with having an `;;;###autoload` cookie on a piece of code which used an
autoloaded macro, so loading `loaddef.el` would cause (auto)loading the
package which provides the macro.

Byte compiling `loaddefs.el` was a way to fix this problem.


        Stefan






  reply	other threads:[~2022-01-03 21:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 23:09 bug#52969: Shortdoc "string" group leads to backtrace Stefan Kangas
2022-01-03  7:34 ` Stefan Kangas
2022-01-03 20:33   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 20:37     ` Lars Ingebrigtsen
2022-01-03 21:05       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 21:19         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-05 15:53         ` Lars Ingebrigtsen
2022-01-05 15:55           ` Lars Ingebrigtsen
2022-01-03 18:56 ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvr19ott7n.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=52969@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.