all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 30078@debbugs.gnu.org
Subject: bug#30078: 27.0.50; Use lexical-binding for M-:
Date: Fri, 12 Jan 2018 21:55:25 +0100	[thread overview]
Message-ID: <87fu7aer0i.fsf@web.de> (raw)
In-Reply-To: <83zi5i26bi.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Jan 2018 22:03:13 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Then you are saying that turning on lexical-binding in *scratch* will
> change nothing at all?  I very much doubt that, and my witness are
> all those packages that broke due to lexical-binding and needed minor
> fixes.

I do what has been proposed for months.  I liked it.

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.

(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.

(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.

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.).

In summary, I think the advantages clearly prevail.


Michael.





  parent reply	other threads:[~2018-01-12 20:55 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 [this message]
2018-01-12 21:04                   ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu7aer0i.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=30078@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 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.