[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emacs-diffs] scratch/raeburn-startup a4231c3 4/5: Don't dump artifa
Re: [Emacs-diffs] scratch/raeburn-startup a4231c3 4/5: Don't dump artifacts of the dump process.
Sun, 16 Apr 2017 23:48:32 -0400
On Apr 12, 2017, at 07:46, Stefan Monnier <address@hidden> wrote:
>> We do have “lexical-binding:t” at the top of the file, but still the
>> let-bound variables’ local bindings are showing up in the output.
> Oh, right, because the lexical-binding:t cookie doesn't take effect
> since we haven't yet loaded the Elisp code which pays attention to it.
This is probably going to make my brain hurt, but… how does that work? At the
point where we do the “let” we’ve already loaded the Lisp code we’re going to
dump. Or is it something that needs to be in effect when we start loading the
file? Maybe something we can explicitly enable after loading the necessary
Lisp bits? If we can’t use lexical binding in loadup.el, maybe we should
change the file header to not appear as though we’re enabling it.
Also, does this issue affect Lisp code loaded as .el source from loadup while