all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24780@debbugs.gnu.org
Subject: bug#24780: 26.0.50; describe-mode lexical-binding
Date: Sat, 27 Jul 2019 10:12:17 -0700 (PDT)	[thread overview]
Message-ID: <26de6e46-deb5-45b6-82b0-8d55800cf26f@default> (raw)
In-Reply-To: <87ftmrvd1p.fsf@gmail.com>

> >> 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 Lexical)
> >
> > when we have lexical binding in the current buffer?  Does anybody
> > have an opinion here?
> 
> IMO it's not worth spending space on the mode line for this.  Yeah,
> sometimes I want to check, and M-< followed by C-u C-SPC to go back
> works fine for that.

+10.  YAGNI.

Emacs itself should avoid adding more stuff to the
mode line.  It should be conservative about that.

In addition to `M-< C-u C-SPC', it's trivial and
quick to do `C-h v lex TAB'.





      parent reply	other threads:[~2019-07-27 17:12 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
2019-07-27 13:10   ` Noam Postavsky
2019-07-27 16:42     ` Lars Ingebrigtsen
2019-07-27 17:12     ` Drew Adams [this message]

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=26de6e46-deb5-45b6-82b0-8d55800cf26f@default \
    --to=drew.adams@oracle.com \
    --cc=24780@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=npostavs@gmail.com \
    /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.