Subject: bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue

From: Eli Zaretskii <[email-masked]>
Date: Wed, 10 Nov 2021 15:20:08 +0200

> From: Emanuel Berg <[email-masked]>
> Cc: [email-masked],  [email-masked]
> 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.