From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 62317@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, teika@gmx.com
Subject: bug#62317: 28.2; This byte-compiled file behaves wrongly.
Date: Wed, 13 Sep 2023 07:02:38 -0700 [thread overview]
Message-ID: <CADwFkm=EBX0nAf=CBK2Aqz8zygj7=P8W3iTvPDfiz1wZv+7CAA@mail.gmail.com> (raw)
In-Reply-To: <jwvzg1r2rif.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> It seems like this patch was never installed.
>
> To be honest, I'm not sure it's worth the trouble.
>
> I'd argue that the bug is in having side-effects like that inside
> `eval-and/when-compile` (or at the top-level of a `require`d file).
> The patch only caters to changes to the `current_buffer` but there can
> be many other ways to cause similar troubles and I can't think of a good
> way to confine them all.
Good point. It seems rather unusual to call `set-buffer' from the
top-level of a required file, to say the least. And if we accept that,
users can start calling all kinds of weird and wonderful things.
On the other hand, the fix seems innocuous enough.
Eli, what do you think? Should we close this as wontfix?
next prev parent reply other threads:[~2023-09-13 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 3:54 bug#62317: 28.2; This byte-compiled file behaves wrongly Teika Kazura
2023-03-22 6:39 ` bug#62317: bug #62317: " Teika Kazura
2023-03-28 9:15 ` Teika Kazura
2023-03-28 12:08 ` Eli Zaretskii
2023-03-28 12:43 ` Andrea Corallo
2023-03-28 12:53 ` Eli Zaretskii
2023-03-28 13:49 ` Andrea Corallo
2023-03-30 9:20 ` Teika Kazura
2023-03-30 9:41 ` Eli Zaretskii
2023-04-01 7:36 ` Teika Kazura
2023-04-01 8:08 ` Eli Zaretskii
2023-04-01 16:27 ` bug#62317: " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-01 17:10 ` Eli Zaretskii
2023-04-01 23:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-02 5:17 ` Eli Zaretskii
2023-09-12 0:08 ` Stefan Kangas
2023-09-12 18:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 14:02 ` Stefan Kangas [this message]
2023-09-13 14:45 ` Eli Zaretskii
2023-09-13 15:46 ` Stefan Kangas
2023-04-01 23:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 0:09 ` Stefan Kangas
2023-04-05 4:12 ` bug#62317: bug #62317: " Teika Kazura
[not found] ` <handler.62317.C.169462003624017.notifdonectrl.0@debbugs.gnu.org>
2023-09-14 6:35 ` bug#62317: acknowledged by developer Teika Kazura
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='CADwFkm=EBX0nAf=CBK2Aqz8zygj7=P8W3iTvPDfiz1wZv+7CAA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=62317@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=teika@gmx.com \
/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).