From: Eli Zaretskii <eliz@gnu.org>
To: LdBeth <andpuke@foxmail.com>
Cc: 64272@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#64272: 28.1; lisp_file_lexically_bound_p behavior mismatches file local variables
Date: Mon, 26 Jun 2023 14:13:36 +0300 [thread overview]
Message-ID: <83a5wmxyqn.fsf@gnu.org> (raw)
In-Reply-To: <tencent_4C24378E6E3BC7D69E340C721D3E2BB63F07@qq.com> (message from LdBeth on Sun, 25 Jun 2023 19:53:09 -0500)
> Date: Sun, 25 Jun 2023 19:53:09 -0500
> From: LdBeth <andpuke@foxmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> LdBeth <andpuke@foxmail.com>,
> 64272@debbugs.gnu.org
>
> >>>>> In <jwvleg7m9ot.fsf-monnier+emacs@gnu.org>
> >>>>> Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > So maybe we should export `lisp_file_lexically_bound_p` to
> > ELisp, let the byte-compiler (and maybe also
> > `emacs-lisp-mode`) verify that it gives the same answer as
> > `hack-local-variables-prop-line`, and emit a loud warning if
> > it doesn't.
>
> I think it is a good idea to have byte-compiler check that.
>
> The context of how this bug reveal is a newbie user
> asked why the lexical-binding does not apply in the .emacs
> file and turns out there is a leading space in the first
> line of the .emacs (well to be honest only scheme people
> does wired things with letrec in their .emacs file)
>
> In the context of sharing .emacs files, the files are not likely to be
> compiled, so it is better also to check that in emacs-lisp-mode, like,
> when the file is opened.
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.
The right solution to such problems is for users to learn not to do
that. Which they already did learn, the first time the bumped into
this. So the problem, such as it is, is already solved, and we still
contemplate it.
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.
next prev parent reply other threads:[~2023-06-26 11:13 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 [this message]
2023-06-26 15:18 ` Gregory Heytings
2023-06-26 15:23 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a5wmxyqn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64272@debbugs.gnu.org \
--cc=andpuke@foxmail.com \
--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 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.