From: Suhail Singh <suhailsingh247@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
christopher@librehacker.com, acm@muc.de,
joostkremers@fastmail.fm, emacs-devel@gnu.org
Subject: Re: Default lexical-binding to t
Date: Fri, 08 Nov 2024 08:12:26 -0500 [thread overview]
Message-ID: <87fro1j2dh.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmn-XKzXmuFagwE9bhqoZeWXb8RHqFZrnk3=k-xH19t45g@mail.gmail.com> (Stefan Kangas's message of "Fri, 8 Nov 2024 12:11:34 +0000")
Stefan Kangas <stefankangas@gmail.com> writes:
>>> • We recommend enabling ‘lexical-binding’ in new code, and converting
>>> existing Emacs Lisp code to enable ‘lexical-binding’ if it doesn't
>>> already. *Note Selecting Lisp Dialect::.
>>
>> I don't think this justifies nagging a user who explicitly wants some
>> file(s) to be treated as using dynamic binding. The above is just a
>> recommendation, not a hard requirement.
>
> I don't consider this as much more than a gentle nudge and reminder.
> The mode line indicator has been with us for a few releases already, and
> I personally don't see compelling reasons to change that decision now.
If the goal, eventually, is to have lexical binding as the default, then
it would help to have all code that uses dynamic binding to (eventually)
use an explicitly set the lexical-binding buffer-local variable. To
that end, while it makes sense to issue a warning for implicit uses of
dynamic binding currently, it is unclear why explicit uses should also
warrant a warning.
I think it would help to distinguish (in the mode line) whether the
dynamic binding is being explicitly requested (which will continue to be
supported in the future) vs when the dynamic binding is the result of a
current default (one that will eventually be changing). Having a
warning face apply _only_ in the latter situation would be a reasonable
approach.
--
Suhail
next prev parent reply other threads:[~2024-11-08 13:12 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:28 Default lexical-binding to t Christopher Howard
2024-11-08 0:38 ` Stefan Kangas
2024-11-08 6:29 ` tomas
2024-11-10 4:04 ` Richard Stallman
2024-11-08 7:27 ` Eli Zaretskii
2024-11-08 12:11 ` Stefan Kangas
2024-11-08 13:12 ` Suhail Singh [this message]
2024-11-08 13:24 ` Stefan Kangas
2024-11-08 13:45 ` Eli Zaretskii
2024-11-08 7:01 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 12:55 Stefan Monnier
2024-11-01 14:42 ` Gerd Möllmann
2024-11-01 17:03 ` Karl Fogel
2024-11-02 10:48 ` Visuwesh
2024-11-02 12:08 ` Eli Zaretskii
2024-11-02 13:21 ` Visuwesh
2024-11-02 16:24 ` Stefan Monnier
2024-11-02 20:42 ` Jim Porter
2024-11-02 21:38 ` Stefan Kangas
2024-11-03 2:32 ` Stefan Kangas
2024-11-03 13:58 ` Stefan Monnier
2024-11-03 14:34 ` Stefan Kangas
2024-11-04 8:35 ` Jean Louis
2024-11-04 8:43 ` tomas
2024-11-03 1:46 ` Stefan Monnier
2024-11-03 2:30 ` Stefan Kangas
2024-11-03 7:47 ` Jim Porter
2024-11-03 13:53 ` Stefan Monnier
2024-11-03 6:44 ` Sean Whitton
2024-11-03 15:26 ` Andrea Corallo
2024-11-07 3:46 ` Richard Stallman
2024-11-07 23:00 ` Andrea Corallo
2024-11-08 15:53 ` Sebastián Monía
2024-11-08 16:23 ` Eli Zaretskii
2024-11-08 17:28 ` Sebastián Monía
2024-11-08 17:37 ` Joost Kremers
2024-11-08 18:51 ` Eli Zaretskii
2024-11-08 20:18 ` Sebastián Monía
2024-11-11 5:13 ` Richard Stallman
2024-11-04 5:34 ` Richard Stallman
2024-11-04 9:39 ` Po Lu
2024-11-04 13:19 ` Eli Zaretskii
2024-11-04 17:06 ` Alfred M. Szmidt
2024-11-06 4:44 ` Richard Stallman
2024-11-07 23:07 ` Andrea Corallo
2024-11-04 12:51 ` Eli Zaretskii
2024-11-05 20:24 ` Stefan Monnier
2024-11-06 12:11 ` Eli Zaretskii
2024-11-06 12:50 ` Stefan Monnier
2024-11-06 13:36 ` Eli Zaretskii
2024-11-06 16:32 ` Stefan Monnier
2024-11-06 17:20 ` Eli Zaretskii
2024-11-06 17:42 ` Alan Mackenzie
2024-11-06 20:48 ` Joost Kremers
2024-11-06 22:50 ` Alan Mackenzie
2024-11-07 0:46 ` Stefan Kangas
2024-11-07 21:03 ` Alan Mackenzie
2024-11-08 0:44 ` Stefan Kangas
2024-11-10 4:04 ` Richard Stallman
2024-11-07 6:14 ` Eli Zaretskii
2024-11-07 8:07 ` Joost Kremers
2024-11-07 8:45 ` Eli Zaretskii
2024-11-07 11:09 ` tomas
2024-11-07 21:23 ` Alan Mackenzie
2024-11-07 22:37 ` Dmitry Gutov
2024-11-08 6:58 ` Eli Zaretskii
2024-11-08 14:01 ` Alan Mackenzie
2024-11-08 15:19 ` Eli Zaretskii
2024-11-08 19:07 ` Alan Mackenzie
2024-11-08 20:01 ` Stefan Monnier
2024-11-07 22:10 ` Andrea Corallo
2024-11-08 18:38 ` Stefan Monnier
2024-11-07 2:55 ` Sean Whitton
2024-11-06 17:54 ` Jim Porter
2024-11-06 19:26 ` Stefan Monnier
2024-11-06 20:23 ` John Yates
2024-11-08 18:43 ` Stefan Monnier
2024-11-06 19:53 ` Jose A. Ortega Ruiz
2024-11-08 18:42 ` Stefan Monnier
2024-11-07 3:46 ` Richard Stallman
2024-11-07 7:09 ` Eli Zaretskii
2024-11-07 3:46 ` Richard Stallman
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=87fro1j2dh.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=acm@muc.de \
--cc=christopher@librehacker.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=stefankangas@gmail.com \
/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.