From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: christopher@librehacker.com, drew.adams@oracle.com,
74261@debbugs.gnu.org
Subject: bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding
Date: Mon, 11 Nov 2024 14:26:51 +0200 [thread overview]
Message-ID: <861pziklbo.fsf@gnu.org> (raw)
In-Reply-To: <E1tAMkB-00009X-AE@fencepost.gnu.org> (message from Richard Stallman on Mon, 11 Nov 2024 00:13:43 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: christopher@librehacker.com, 74261@debbugs.gnu.org, eliz@gnu.org
> Date: Mon, 11 Nov 2024 00:13:43 -0500
>
> > 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.
I tend to agree, but only if the file does not already have a
lexical-binding cookie which makes the file use dynamical binding.
Compare this with files that have an unusual encoding or an EOL format
that is not the native one on the current platform: we provide an
indication on the mode line, but don't insist on having it stand out
too much, just a little.
next prev parent reply other threads:[~2024-11-11 12:26 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
2024-11-11 12:26 ` Eli Zaretskii [this message]
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=861pziklbo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74261@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=drew.adams@oracle.com \
--cc=rms@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.