From: LdBeth <andpuke@foxmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64272@debbugs.gnu.org, LdBeth <andpuke@foxmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#64272: 28.1; lisp_file_lexically_bound_p behavior mismatches file local variables
Date: Sat, 24 Jun 2023 21:11:11 -0500 [thread overview]
Message-ID: <tencent_BAFFD4DC56BA8B1D057BA430747402AD2609@qq.com> (raw)
In-Reply-To: <83zg4oy9ow.fsf@gnu.org>
>>>>> In <83zg4oy9ow.fsf@gnu.org>
>>>>> Eli Zaretskii <eliz@gnu.org> wrote:
ldb> This behavior is in contrast to how file local variables are applied
ldb> when opening a file, that is, as long as the variable list is in
ldb> the first line, it is applied.
ldb>
ldb> Either the documentation should bring up this behavior, or the
ldb> C function `lisp_file_lexically_bound_p' in `src/lread.c' should be fixed.
Eli> I think we should do the latter, because
Eli> hack-local-variables-prop-line is more lenient than
Eli> lisp_file_lexically_bound_p.
Eli> Stefan, any comments?
If so, I think the only thing needs to be changed is
remove the `if (ch != ';')` test.
Since from what I test, even if first line is something like
|(setq tmp " -*- lexical-binding: t -*- ")
the file local variables would still be applied.
---
ldb
next prev parent reply other threads:[~2023-06-25 2:11 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 [this message]
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
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=tencent_BAFFD4DC56BA8B1D057BA430747402AD2609@qq.com \
--to=andpuke@foxmail.com \
--cc=64272@debbugs.gnu.org \
--cc=eliz@gnu.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).