From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 24780@debbugs.gnu.org
Subject: bug#24780: 26.0.50; describe-mode lexical-binding
Date: Sat, 27 Jul 2019 14:58:53 +0200 [thread overview]
Message-ID: <87y30jhbw2.fsf@mouse.gnus.org> (raw)
In-Reply-To: <accf787e-200d-63a7-77c9-1bec3b1a2b6b@easy-emacs.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6hler\=22's\?\= message of "Mon, 24 Oct 2016 11:13:32 +0200")
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> consider it useful if `describe-mode' reports value of var
> `lexical-binding'.
Hm... That command describes the mode, and whether the current .el file
uses lexical binding or not isn't really tied to the mode, so I think
that sounds a bit confusing. The user may believe that we're talking
about whether the mode uses lexical binding or not.
> Even displaying it in mode-line might be an option.
That does sound more useful -- I often find jumping back to the start of
the buffer to check.
`emacs-lisp-mode' could display that somewhere in the mode line, I
guess? But where? Perhaps among the U:**- thing at the start? Or in
the mode stuff?
So instead of
(Emacs-Lisp)
we'd get
(Emacs-Lisp Lexical)
when we have lexical binding in the current buffer? Does anybody have
an opinion here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-27 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 9:13 bug#24780: 26.0.50; describe-mode lexical-binding Andreas Röhler
[not found] ` <mailman.2389.1564232406.2688.bug-gnu-emacs@gnu.org>
2019-07-27 12:19 ` Alan Mackenzie
2020-08-12 1:06 ` Stefan Kangas
2020-08-12 10:52 ` Lars Ingebrigtsen
2020-08-12 10:56 ` Lars Ingebrigtsen
2020-08-12 13:10 ` Stefan Kangas
2020-08-12 13:14 ` Lars Ingebrigtsen
2020-08-12 14:03 ` Stefan Kangas
2019-07-27 12:58 ` Lars Ingebrigtsen [this message]
2019-07-27 13:10 ` Noam Postavsky
2019-07-27 16:42 ` Lars Ingebrigtsen
2019-07-27 17:12 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y30jhbw2.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=24780@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).