From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: luangruo@yahoo.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Declaring 'lexical-binding: nil' obsolete
Date: Sun, 26 Sep 2021 09:06:16 +0300 [thread overview]
Message-ID: <8335prq3af.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnmLw_KgJSCQruYnHk+gSJVAV9WggTqs_rw+Y+EPZKNtg@mail.gmail.com> (message from Stefan Kangas on Sat, 25 Sep 2021 17:04:46 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 25 Sep 2021 17:04:46 -0700
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Emacs developers <emacs-devel@gnu.org>
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > But countless amounts of user code might be made obsolete by this
> > change, including a great deal of my own. And I (and presumably other
> > people) will have no time to adjust to this change.
>
> The roadmap I propose will give you a decade or so to adjust, and even
> then will you only need to change one line per ELisp file for it to work
> just as it does today.
>
> Before then, the worst that will happen is that you will see a warning.
Unwarranted warnings are baaad... Especially when there's nothing
wrong with the code, really.
next prev parent reply other threads:[~2021-09-26 6:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 22:47 Declaring 'lexical-binding: nil' obsolete Stefan Kangas
2021-09-25 23:17 ` Po Lu
2021-09-26 0:04 ` Stefan Kangas
2021-09-26 0:13 ` Po Lu
2021-09-26 0:50 ` Stefan Kangas
2021-09-26 1:20 ` Po Lu
2021-09-26 2:37 ` Stefan Kangas
2021-09-26 2:55 ` Po Lu
2021-09-26 6:30 ` Eli Zaretskii
2021-09-26 6:08 ` Eli Zaretskii
2021-09-26 6:06 ` Eli Zaretskii [this message]
2021-09-25 23:56 ` Eduardo Ochs
2021-09-26 0:35 ` Stefan Kangas
2021-09-26 6:02 ` Eli Zaretskii
2021-09-26 6:36 ` Lars Ingebrigtsen
2021-09-27 22:35 ` Deprecating 'lexical-binding: nil' Richard Stallman
2021-09-27 23:09 ` Stefan Kangas
2021-09-28 1:42 ` Stefan Monnier
2021-09-30 6:03 ` Richard Stallman
2021-09-30 14:18 ` Steingold
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=8335prq3af.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.