unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24780@debbugs.gnu.org
Subject: bug#24780: 26.0.50; describe-mode lexical-binding
Date: 27 Jul 2019 12:19:02 -0000	[thread overview]
Message-ID: <20190727121902.22177.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.2389.1564232406.2688.bug-gnu-emacs@gnu.org>

Hello, Lars.

In article <mailman.2389.1564232406.2688.bug-gnu-emacs@gnu.org> you wrote:
> 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?

Yes.  "Lexical" is too long, considering its relative lack of
importance.  Space on the mode line is precious, particularly when
running Follow Mode.  Also, "Lexical" isn't really a minor mode, so
shouldn't look like one.

How about, instead,

    (Emacs-Lisp/L)

or

    (Emacs-Lisp/D)

?  Even that is going to be a nuisance to some people, so it really
needs a user option to turn it off.

> -- 
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2019-07-27 12:19 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 [this message]
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
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=20190727121902.22177.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=24780@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).