From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54381@debbugs.gnu.org, paaguti@gmail.com
Subject: bug#54381: 29.0.50; Automatically load custom-file
Date: Mon, 14 Mar 2022 15:15:50 +0200 [thread overview]
Message-ID: <83r174k73t.fsf@gnu.org> (raw)
In-Reply-To: <877d8wooh4.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 14 Mar 2022 10:47:03 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 14 Mar 2022 10:47:03 +0100
> Cc: 54381@debbugs.gnu.org
>
> So if we add this user option, it'll have to default to nil, and in that
> case I don't see much point in the user option. (Because people will
> have to `setq' it in their init files.)
I agree.
> If we introduced the `custom-file' variable today, we'd load it
> automatically, but I don't think it's possible to do so now without
> breaking stuff.
>
> Anybody else got an opinion?
Would it perhaps help if we could support automatic loading of the
custom file if its basename was something special, or perhaps one of a
small number of fixed names? If we choose a name that is unlikely to
be in wide use, all people will need is to rename their files (and
modify the init file).
next prev parent reply other threads:[~2022-03-14 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 8:21 bug#54381: 29.0.50; Automatically load custom-file Pedro Andres Aranda Gutierrez
2022-03-14 9:47 ` Lars Ingebrigtsen
2022-03-14 9:48 ` Lars Ingebrigtsen
2022-03-14 15:14 ` bug#54381: [External] : " Drew Adams
2022-03-14 13:15 ` Eli Zaretskii [this message]
2022-03-14 15:26 ` Robert Pluim
2022-03-14 16:19 ` Pedro Andres Aranda Gutierrez
2022-03-14 16:36 ` Robert Pluim
2022-03-14 16:47 ` Pedro Andres Aranda Gutierrez
2022-03-14 17:53 ` Robert Pluim
2022-03-15 7:51 ` Pedro Andres Aranda Gutierrez
2022-03-14 13:58 ` Robert Pluim
2022-04-14 14:05 ` Lars Ingebrigtsen
2022-03-17 6:38 ` bug#54381: Handling a corner case Pedro Andres Aranda Gutierrez
2022-03-17 7:09 ` Pedro Andres Aranda Gutierrez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r174k73t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54381@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=paaguti@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.