GNU bug report logs - #78304
31.0.50; Support --early-eval on the command line

Previous Next

Full log

View this message in rfc822 format

From: Ship Mints <shipmints <at> gmail.com>
To: Spencer Baugh <sbaugh <at> janestreet.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 78304 <at> debbugs.gnu.org
Subject: bug#78304: 31.0.50; Support --early-eval on the command line
Date: Wed, 14 May 2025 14:40:53 -0400

[Message part 1 (text/plain, inline)]

On Wed, May 14, 2025 at 2:34 PM Spencer Baugh <sbaugh <at> janestreet.com> wrote:

> Ship Mints <shipmints <at> gmail.com> writes:
>
> > On Wed, May 14, 2025 at 1:57 PM Spencer Baugh via Bug reports for GNU
> Emacs, the Swiss army knife of text editors
> > <bug-gnu-emacs <at> gnu.org> wrote:
> >  How about this variation on your idea: what if we added a
> >  site-early-start.el which is loaded just before early-init.el, mirroring
> >  how site-start.el is loaded just before init.el?  That would be really
> >  useful for my site in general, for more than just this issue, because it
> >  would allow new kinds of site-wide configuration that is currently
> >  impossible.
> >
> > That's good.  Wouldn't you want both that and a command-line option like
> -qe so that you can do this via the command line to aid
> > testing and also provide Emacs programs that don't rely on
> site-early-init.el?
>
> No, site-early-init.el would remove the need for -qe: simply export the
> environment variable "EMACSLOADPATH=somedir:" where somedir contains a
> site-early-init.el file which has the code you want to run "early", and
> then pass -q as normal.
>
> More awkward, of course, but it would work fine.
>

And a little less discoverable.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.