unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Loading early-init.el in batch mode (was: package-update-all from command line)
Date: Tue, 24 May 2022 21:58:38 +0300	[thread overview]
Message-ID: <831qwi69lt.fsf@gnu.org> (raw)
In-Reply-To: <jwvfskznczh.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 24 May 2022 12:00:40 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Tue, 24 May 2022 12:00:40 -0400
> 
> > given that we don't limit users in what should go into that file.
> 
> We don't give guidelines, but by virtue of it being loaded before the
> GUI is setup, it does have similar technical limitations to the ones
> that apply for batch uses.

Not really: quite a lot of GUI-related settings can be done before the
GUI setup is done.

> > If you want a special init file for batch sessions, we should
> > introduce a special file and document it as reserved only for settings
> > that are supposed to work in -batch sessions.
> 
> We could, indeed.  I can't think of any reason why we wouldn't want to
> load that same file in interactive sessions, tho (IOW, I can't think of
> too many user settings which would  be useful for batch use and
> undesirable for interactive use).

That'd be risking problems that can be avoided.  If we document that
file as being loaded only by batch sessions, we won't need to solve
bugs where people loaded it in interactive sessions and that didn't do
what they expected.

> If we add such a file, we should be careful to allow something like
> `--batch -q` to prevent loading that file.

Probably.



  reply	other threads:[~2022-05-24 18:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  3:42 package-update-all from command line Sam Steingold
2022-05-24 13:54 ` Stefan Monnier
2022-05-24 14:05   ` Eli Zaretskii
2022-05-24 16:00     ` Loading early-init.el in batch mode (was: package-update-all from command line) Stefan Monnier
2022-05-24 18:58       ` Eli Zaretskii [this message]
2022-05-24 15:04   ` package-update-all from command line Sam Steingold
2022-05-24 15:52     ` Stefan Monnier
2022-05-24 19:01       ` Sam Steingold
2022-05-24 19:55         ` Stefan Monnier
2022-05-25 15:14           ` Sam Steingold
2022-05-25 16:13             ` Stefan Monnier
2022-05-26 15:13               ` Sam Steingold
2022-05-26 15:35                 ` Stefan Monnier
2022-05-25  1:26 ` Lars Ingebrigtsen
2022-05-25  4:58   ` Tassilo Horn
2022-05-25 12:05     ` Lars Ingebrigtsen
2022-05-25 12:27       ` Tassilo Horn
2022-05-27 10:21         ` Lars Ingebrigtsen
2022-05-27 20:33           ` Tassilo Horn

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=831qwi69lt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).