From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 64272@debbugs.gnu.org, andpuke@foxmail.com, monnier@iro.umontreal.ca
Subject: bug#64272: 28.1; lisp_file_lexically_bound_p behavior mismatches file local variables
Date: Mon, 26 Jun 2023 18:23:23 +0300 [thread overview]
Message-ID: <83sfaew8lw.fsf@gnu.org> (raw)
In-Reply-To: <30832e8647ddb7b160e5@heytings.org> (message from Gregory Heytings on Mon, 26 Jun 2023 15:18:34 +0000)
> Date: Mon, 26 Jun 2023 15:18:34 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: LdBeth <andpuke@foxmail.com>, 64272@debbugs.gnu.org,
> monnier@iro.umontreal.ca
>
> > I'm sorry to bust this particular wedding, but here we see once again
> > what became a frequent pattern in Emacs: a tiny problem, perhaps
> > affecting one or a few users who happen to bump into it the first time
> > they try something, which then causes quite serious changes to low-level
> > infrastructure in Emacs that has been working flawlessly for years, and
> > by doing that destabilize Emacs for no good reason. IOW, a tail that
> > wags the dog.
> >
> > Happens time and again in Emacs, and we all fail to pay attention.
> >
> > [...]
> >
> > That said, I know I will be downvoted, and so will not object any
> > changes in this wrong direction. Let the resultant breakage speak for
> > itself.
> >
>
> Not that my opinion counts, but FWIW, I agree with the above, and I upvote
> this.
Thank you! (And your opinion does count, at least here.)
next prev parent reply other threads:[~2023-06-26 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 18:22 bug#64272: 28.1; lisp_file_lexically_bound_p behavior mismatches file local variables LdBeth
2023-06-24 18:52 ` Eli Zaretskii
2023-06-24 19:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 2:11 ` LdBeth
2023-06-25 6:08 ` Eli Zaretskii
2023-06-25 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 15:02 ` Eli Zaretskii
2023-06-25 15:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 17:17 ` LdBeth
2023-06-25 18:16 ` Eli Zaretskii
2023-06-25 23:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-26 0:53 ` LdBeth
2023-06-26 11:13 ` Eli Zaretskii
2023-06-26 15:18 ` Gregory Heytings
2023-06-26 15:23 ` Eli Zaretskii [this message]
2023-11-21 13:12 ` Gerd Möllmann
2023-06-26 10:59 ` Eli Zaretskii
2023-06-25 23:16 ` LdBeth
2023-06-26 0:45 ` LdBeth
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=83sfaew8lw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64272@debbugs.gnu.org \
--cc=andpuke@foxmail.com \
--cc=gregory@heytings.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).