From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: monnier@IRO.UMontreal.CA, 30078@debbugs.gnu.org
Subject: bug#30078: 27.0.50; Use lexical-binding for M-:
Date: Fri, 12 Jan 2018 23:04:56 +0200 [thread overview]
Message-ID: <83y3l223gn.fsf@gnu.org> (raw)
In-Reply-To: <87fu7aer0i.fsf@web.de> (message from Michael Heerdegen on Fri, 12 Jan 2018 21:55:25 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 30078@debbugs.gnu.org
> Date: Fri, 12 Jan 2018 21:55:25 +0100
>
> What are we doing with scratch?
>
> (1) Setting global variables, defining small functions and such simple
> stuff. lexical-binding doesn't make a big difference here.
We need to discuss the differences whether they are big or not.
> (2) Re-evaluate parts of the source code, often with small
> modifications, for testing and debugging. Since more and more packages
> make active use of lexical-binding, this is actually broken currently!
> Re-evaluating parts of source code in scratch can currently break Emacs.
You are describing a mistake. People make mistakes all the time, and
will continue making mistakes whatever we do. That shouldn't be a
basis for our decisions.
> (3) I often posted some code examples in emacs-help which made use of
> lexical-binding. People pasted it into scratch and it didn't work.
> It's currently even not trivial to evaluate such examples with
> lexical-binding on.
Another mistake. I don't see why this should be of any importance for
the decision at hand.
> OTOH, there is not too much code that really relies on dynamical binding
> mode. And very often, such code is just written in a bad style (missing
> `defvar's etc.).
That's your opinion. I happen not to share it.
> In summary, I think the advantages clearly prevail.
I actually didn't yet see any advantages mentioned, and the above
aren't, IMO. Lexical-binding is just a feature, albeit an important
one. It doesn't have to be introduced into every possible corner of
Emacs, not without a good reason.
next prev parent reply other threads:[~2018-01-12 21:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 16:36 bug#30078: 27.0.50; Use lexical-binding for M-: Stefan Monnier
2018-01-11 20:58 ` Michael Heerdegen
2018-01-12 14:58 ` Stefan Monnier
2018-01-12 16:12 ` Stefan Monnier
2018-01-12 16:53 ` Glenn Morris
2018-01-12 17:23 ` Michael Heerdegen
2018-01-12 18:47 ` Stefan Monnier
2018-01-12 19:35 ` Michael Heerdegen
2018-01-13 17:58 ` Stefan Monnier
2018-01-12 18:34 ` Eli Zaretskii
2018-01-12 18:49 ` Stefan Monnier
2018-01-12 18:55 ` Eli Zaretskii
2018-01-12 19:06 ` Stefan Monnier
2018-01-12 20:03 ` Eli Zaretskii
2018-01-12 20:33 ` Noam Postavsky
2018-01-12 20:55 ` Michael Heerdegen
2018-01-12 21:04 ` Eli Zaretskii [this message]
2018-01-12 21:11 ` Michael Heerdegen
2018-01-13 17:50 ` Luis Gerhorst
2018-01-13 19:48 ` Eli Zaretskii
2018-01-13 20:19 ` Luis Gerhorst
2018-01-14 5:58 ` Robert Cochran
2018-01-13 18:19 ` Stefan Monnier
2018-01-13 19:34 ` Eli Zaretskii
2018-01-13 21:58 ` Stefan Monnier
2018-01-13 23:18 ` Richard Stallman
2018-01-14 2:07 ` Drew Adams
2018-01-15 2:34 ` Richard Stallman
2018-01-13 18:05 ` Stefan Monnier
2018-01-13 19:37 ` Eli Zaretskii
2018-03-19 19:32 ` Stefan Monnier
2018-03-19 19:34 ` Stefan Monnier
2018-03-19 20:10 ` Eli Zaretskii
2018-03-19 20:50 ` Stefan Monnier
2018-03-20 6:59 ` Eli Zaretskii
2018-03-20 19:20 ` Stefan Monnier
2018-04-02 19:40 ` Richard Stallman
2018-04-03 0:12 ` Stefan Monnier
2018-04-03 16:50 ` Richard Stallman
[not found] <mailman.7210.1515688689.27995.bug-gnu-emacs@gnu.org>
2018-01-12 16:28 ` nazienham
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=83y3l223gn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30078@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
/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).