GNU bug report logs - #64272
28.1; lisp_file_lexically_bound_p behavior mismatches file local variables

Previous Next

Full log

View this message in rfc822 format

From: LdBeth <andpuke <at> foxmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 64272 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>, LdBeth <andpuke <at> foxmail.com>
Subject: bug#64272: 28.1; lisp_file_lexically_bound_p behavior mismatches file local variables
Date: Sun, 25 Jun 2023 19:53:09 -0500

>>>>> In <jwvleg7m9ot.fsf-monnier+emacs <at> gnu.org> 
>>>>>	Stefan Monnier <monnier <at> 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.

---
ldb

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.