From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53024@debbugs.gnu.org, schwab@linux-m68k.org, monnier@iro.umontreal.ca
Subject: bug#53024: 29.0.50; Wishlist: Byte-compile loaddefs.el?
Date: Tue, 02 Aug 2022 14:17:20 +0300 [thread overview]
Message-ID: <83ilna28u7.fsf@gnu.org> (raw)
In-Reply-To: <87bkt32cr0.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 02 Aug 2022 11:52:51 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: schwab@linux-m68k.org, 53024@debbugs.gnu.org, monnier@iro.umontreal.ca
> Date: Tue, 02 Aug 2022 11:52:51 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but where are those subtle points documented? We need them
> > documented so that we don't break this again in the future.
>
> It was just a bug, so I'm not sure where you'd document something like
> that.
Your fix for that problem, AFAIU, was to replace a simple literal
'insert' with something else, and I thought the considerations for
doing one and not the other should be spelled out somewhere.
next prev parent reply other threads:[~2022-08-02 11:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 15:53 bug#53024: 29.0.50; Wishlist: Byte-compile loaddefs.el? Lars Ingebrigtsen
2022-01-22 12:27 ` Lars Ingebrigtsen
2022-07-31 10:02 ` Lars Ingebrigtsen
2022-07-31 10:19 ` Lars Ingebrigtsen
2022-07-31 10:47 ` Lars Ingebrigtsen
2022-07-31 16:35 ` Lars Ingebrigtsen
2022-07-31 17:06 ` Andreas Schwab
2022-08-01 12:33 ` Lars Ingebrigtsen
2022-08-01 13:06 ` Eli Zaretskii
2022-08-02 9:52 ` Lars Ingebrigtsen
2022-08-02 11:17 ` Eli Zaretskii [this message]
2022-08-02 11:19 ` Lars Ingebrigtsen
2022-08-03 12:24 ` Lars Ingebrigtsen
2022-08-03 12:41 ` Lars Ingebrigtsen
2022-08-04 6:07 ` Lars Ingebrigtsen
2022-08-04 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:46 ` Lars Ingebrigtsen
2022-08-05 12:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 12:22 ` Lars Ingebrigtsen
2022-08-05 13:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 12:10 ` Lars Ingebrigtsen
2022-08-04 16:31 ` Andreas Schwab
2022-08-04 16:37 ` Lars Ingebrigtsen
2022-08-04 17:10 ` Eli Zaretskii
2022-08-04 17:14 ` Lars Ingebrigtsen
2022-08-04 17:22 ` Eli Zaretskii
2022-08-05 11:44 ` Lars Ingebrigtsen
2022-08-05 12:57 ` Eli Zaretskii
2022-08-06 12:09 ` Lars Ingebrigtsen
2022-08-06 12:16 ` Eli Zaretskii
2022-08-06 12:20 ` Lars Ingebrigtsen
2022-08-04 18:08 ` Andreas Schwab
2022-08-04 18:11 ` Lars Ingebrigtsen
2022-08-04 19:15 ` Andreas Schwab
2022-08-04 19:20 ` Lars Ingebrigtsen
2022-08-04 20:17 ` Andreas Schwab
2022-08-04 20:31 ` Lars Ingebrigtsen
2022-08-04 20:57 ` Lars Ingebrigtsen
2022-08-05 5:44 ` Eli Zaretskii
2022-08-05 11:51 ` Lars Ingebrigtsen
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=83ilna28u7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53024@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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.
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).