From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 67916@debbugs.gnu.org, "Philip Kaludercic" <philipk@posteo.net>,
"Mattias Engdegård" <mattias.engdegard@gmail.com>
Subject: bug#67916: 30.0.50; No lexical-binding directive warning in -pkg.el files
Date: Wed, 20 Dec 2023 15:43:28 -0500 [thread overview]
Message-ID: <jwv1qbgd2ws.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8734vwkaqi.fsf@epfl.ch> (Basil L. Contovounesios's message of "Wed, 20 Dec 2023 19:08:37 +0100")
> I'm wondering because elpa-admin.el seems to contain some compatibility
> code for Emacs 26 (elpaa--select-revision, elpaa--write-pkg-file) and
> Emacs versions <28 (elpaa--get-section, elpaa--html-build-doc).
AFAIK `elpa-admin.el` is mostly used with "Emacs from Debian stable" (in
`elpa.gnu.org`) and with the bleeding edge of Emacs, so backward
compatibility is not very important beyond Emacs-28 now. The one you
see is what was added at the time and simply hasn't been removed (yet).
> You mean, you prefer package--unquote being a plain function?
> [ To be honest, I'm slightly inclined to add this to macroexp.el
> instead, since it's a somewhat common operation. ]
Usually in the context of macro expansion you can use `eval` for that.
Here we don't, for (arguably bogus) "security" reasons.
Stefan
prev parent reply other threads:[~2023-12-20 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 21:49 bug#67916: 30.0.50; No lexical-binding directive warning in -pkg.el files Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-19 22:15 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-20 15:14 ` Philip Kaludercic
2023-12-20 18:08 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-20 18:54 ` Philip Kaludercic
2023-12-20 20:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=jwv1qbgd2ws.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=67916@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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.