GNU bug report logs - #70068
[PATCH] Don't warn about lexical binding in lisp-interaction-mode

Previous Next

Package: emacs;

Reported by: Philip Kaludercic <philipk <at> posteo.net>

Date: Fri, 29 Mar 2024 11:33:02 UTC

Severity: normal

Tags: patch

Done: Philip Kaludercic <philipk <at> posteo.net>

Bug is archived. No further changes may be made.

Full log


Message #14 received at 70068 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, 70068 <at> debbugs.gnu.org
Subject: Re: bug#70068: [PATCH] Don't warn about lexical binding in
 lisp-interaction-mode
Date: Sat, 30 Mar 2024 15:54:30 +0300
> From: Philip Kaludercic <philipk <at> posteo.net>
> Cc: 70068 <at> debbugs.gnu.org
> Date: Sat, 30 Mar 2024 11:07:00 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Philip Kaludercic <philipk <at> posteo.net>
> >> Date: Fri, 29 Mar 2024 11:31:49 +0000
> >> 
> >> The main intention here is to avoid underlining the first line in the
> >> *scratch* buffer when flymake is enabled:
> >
> > If this is the goal, why such a general change?  Wouldn't it be better
> > to special-case *scratch* in Flymake instead?  Making such
> > generalizations runs the risk of unintended consequences.
> 
> My thinking was that one never needs to set the variable anyway, since
> `lisp-interaction-mode' sets `lexical-binding' anyway.  Alternatively,
> one could also modify the patch to check if `lexical-binding' is non-nil?

The latter possibility would be better, I think.  Stefan, WDYT?




This bug report was last modified 1 year and 38 days ago.

Previous Next


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