all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Christopher Howard <christopher@librehacker.com>,
	"74261@debbugs.gnu.org" <74261@debbugs.gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding
Date: Fri, 8 Nov 2024 18:05:02 +0000	[thread overview]
Message-ID: <DS7PR10MB52322C9EFB8C79B1C740C2CFF35D2@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87h68hzqmw.fsf@librehacker.com>

+1.
____

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.

This consideration is appropriate regardless
of whether the default in Emacs is (like now)
dynamic binding or (in the future) lexical
binding.

Just let users know what mode the buffer is
in.  And make it easy for users to not show
any such indication, if they like.  Provide
a new mode-line variable for the indication:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Mode-Line-Variables.html

(Such a variable should have been introduced
when the indication was first added...)

  reply	other threads:[~2024-11-08 18:05 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 [this message]
2024-11-11  5:13   ` Richard Stallman
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=DS7PR10MB52322C9EFB8C79B1C740C2CFF35D2@DS7PR10MB5232.namprd10.prod.outlook.com \
    --to=bug-gnu-emacs@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.