From: Eli Zaretskii <eliz@gnu.org>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: 51695@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue
Date: Wed, 10 Nov 2021 15:20:08 +0200 [thread overview]
Message-ID: <837ddg406v.fsf@gnu.org> (raw)
In-Reply-To: <87a6ic23ie.fsf@zoho.eu> (message from Emanuel Berg on Wed, 10 Nov 2021 02:39:05 +0100)
> From: Emanuel Berg <moasenwood@zoho.eu>
> Cc: 51695@debbugs.gnu.org, monnier@iro.umontreal.ca
> Date: Wed, 10 Nov 2021 02:39:05 +0100
>
> > How can the interactive spec use lexically-bound variables
> > outside its scope, when the interactive spec runs not at
> > function definition time, but at function invocation time,
> > when those variables will be long gone?
>
> But it does work if you evaluate the code, isn't this
> discrepancy a problem?
Not for me, it isn't. But what do I know?
> "Function definition time", is that the time of Elisp
> evaluation, byte compilation, or the loading of byte-compiled
> source BTW?
Whenever the function definition is evaluated, yes.
next prev parent reply other threads:[~2021-11-10 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 23:40 bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 12:29 ` Eli Zaretskii
2021-11-10 1:39 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 1:54 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 13:20 ` Eli Zaretskii [this message]
2021-11-09 13:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 23:32 ` Michael Heerdegen
2021-11-10 1:50 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 4:13 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 23:44 ` Michael Heerdegen
2021-11-11 1:55 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-11 4:14 ` Michael Heerdegen
2022-09-20 12:13 ` Lars Ingebrigtsen
2022-09-23 20:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-24 10:31 ` Lars Ingebrigtsen
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=837ddg406v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51695@debbugs.gnu.org \
--cc=moasenwood@zoho.eu \
--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).