From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: christopher@librehacker.com, eliz@gnu.org, 74261@debbugs.gnu.org
Subject: bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding
Date: Mon, 11 Nov 2024 00:13:43 -0500 [thread overview]
Message-ID: <E1tAMkB-00009X-AE@fencepost.gnu.org> (raw)
In-Reply-To: <DS7PR10MB52322C9EFB8C79B1C740C2CFF35D2@DS7PR10MB5232.namprd10.prod.outlook.com> (bug-gnu-emacs@gnu.org)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The indication in the mode line should be
> (1) optional and (2) unobtrusive.
> #2: it should just matter-of-factly tell you
> what mode the current buffer is in.
I contend it should be "intrusive" enough to serve as an effective
reminder.
Once dynamic binding becomes unusual, programmers will tend to
assume without conscious doubt that every file uses lexical binding.
So I think that the indicator that this file uses dynamic binding
ought to be somewhat loud, so that users won't overlook it.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-11-11 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:33 bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding Christopher Howard
2024-11-08 18:05 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-11 5:13 ` Richard Stallman [this message]
2024-11-11 12:26 ` Eli Zaretskii
2024-11-25 4:32 ` Richard Stallman
2024-11-25 12:20 ` Eli Zaretskii
2024-11-28 4:54 ` Richard Stallman
2024-11-28 9:40 ` Eli Zaretskii
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=E1tAMkB-00009X-AE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=74261@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
/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.