Re: missing lexical-binding cookie warning when loading .el files

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 04 May 2024 12:05:04 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: mattias.engdegard@gmail.com, emacs-devel@gnu.org
> 
> > From: Po Lu <luangruo@yahoo.com>
> > Cc: mattias.engdegard@gmail.com,  emacs-devel@gnu.org
> > Date: Sat, 04 May 2024 16:23:09 +0800
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > > Those are under user-emacs-directory, right?
> > 
> > Correct.  My point was that presumably the warning is appropriate for at
> > least the early-init file, and possibly also for the init file, when it
> > is not generated by such mechanisms as Custom.
> 
> I disagree.  I think we shouldn't bug users due to their init files,
> not at all.
> 
> So I think at this point we could either (a) exempt all files below
> user-emacs-directory, (b) add a database of basenames of files that
> should be exempt from these warnings, or (c) a combination of those
> two.
> 
> Any other suggestions?

I see Mattias already installed something, without waiting for the
discussion to come to conclusions.

But IMO the installed change is incorrect/incomplete:

  . it hard-codes ".emacs" as the file for which we don't warn, thus
    leaving the warning in effect for early-init files
  . the init file can be named init.el or _emacs (with or without
    .el), and the change doesn't handle that
  . there are files like recentf-save-file (default: ".recentf") or
    abbrev-file-name (default: "abbrev_defs") and others, which should
    also be exempt of this

I wish people would discuss such changes before committing them.  This
is a complex issue, with many aspects that are not really obvious, as
Emacs loads files in many contexts and for many different purposes.
We should be sure we understand all the aspects before we design and
implement solutions.