From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: 39823@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#39823: 26.3; update-directory-autoloads regression from Emacs 26 to Emacs 27
Date: Mon, 16 Mar 2020 22:16:04 -0400 [thread overview]
Message-ID: <87y2rz4tgb.fsf@gmail.com> (raw)
In-Reply-To: <E1jCxZY-0007qj-Iq@fencepost.gnu.org> (Richard Stallman's message of "Fri, 13 Mar 2020 23:34:48 -0400")
Hello,
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> Is there any real use for lexical scoping in --eval?
> I suggest reverting the default for --eval to dynamic.
> We could introduce --evallex to specify lexical scoping
> and ask people to tell us if they find it useful.
Not a bad suggestion, but I actually embrace the change to lexical mode
everywhere (I find it more forward looking, and like that it is
consistently the default everywhere). I believe the reason for this bug
report is two-fold:
1) I wasn't aware of the change to --eval (my bad -- I don't follow
Emacs development very closely).
2) The API of some older code (such as the `update-directory-autoloads'
procedure from the autoload library, as I found out) requires the use of
dynamic evaluation for its API to function.
Now that I know about 1), it's rather easy to work around 2). And I'd
guess that with Elisp finally preferring lexical scope by default, 2)
will tend to disappear over time.
Maxim
next prev parent reply other threads:[~2020-03-17 2:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:11 bug#39823: 26.3; update-directory-autoloads regression from Emacs 26 to Emacs 27 Maxim Cournoyer
2020-03-13 0:43 ` Noam Postavsky
2020-03-13 8:30 ` Eli Zaretskii
2020-03-14 2:06 ` Maxim Cournoyer
2020-03-13 23:01 ` Michael Heerdegen
2020-03-14 2:03 ` Maxim Cournoyer
2020-03-17 11:48 ` Noam Postavsky
2020-03-14 3:34 ` Richard Stallman
2020-03-17 2:16 ` Maxim Cournoyer [this message]
2020-03-19 1:46 ` Richard Stallman
2020-04-08 3:55 ` Maxim Cournoyer
2020-04-08 6:31 ` Eli Zaretskii
2020-04-08 16:41 ` Maxim Cournoyer
2020-04-08 19:09 ` Eli Zaretskii
2020-04-19 3:13 ` Maxim Cournoyer
2020-04-19 12:19 ` Noam Postavsky
2020-06-22 4:10 ` Maxim Cournoyer
2020-06-22 15:07 ` Noam Postavsky
2020-06-23 20:42 ` Maxim Cournoyer
2020-09-30 15:23 ` Lars Ingebrigtsen
2020-10-01 17:20 ` Lars Ingebrigtsen
2020-10-01 17:54 ` Eli Zaretskii
2020-10-01 18:06 ` Lars Ingebrigtsen
2020-10-02 2:36 ` Lars Ingebrigtsen
2020-10-02 17:54 ` Maxim Cournoyer
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=87y2rz4tgb.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=39823@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=rms@gnu.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).