From: Rudolf Schlatte <rudi@constantly.at>
To: 49424@debbugs.gnu.org
Subject: bug#49424: 27.2; Misdocumented default initialisation file
Date: Wed, 07 Jul 2021 18:33:31 +0200 [thread overview]
Message-ID: <m2v95mxew4.fsf@constantly.at> (raw)
In-Reply-To: <w53wnq4id3h.fsf@froglet.home.mavit.org.uk>
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Wed, 07 Jul 2021 13:28:30 +0200, Rudolf Schlatte <rudi@constantly.at> said:
>
> Rudolf> Robert Pluim <rpluim@gmail.com> writes:
>
> >> Emacs will prefer the XDG path if it exists and .emacs.d/init.el and
> >> .emacs donʼt. Similarly Emacs will prefer .emacs.d/init.el if it
> >> exists and .emacs doesnʼt.
>
> Rudolf> I wonder if it would make sense to warn during startup if more than one
> Rudolf> of these files exist, something like: "Warning: multiple init files
> Rudolf> detected. Using ~/.emacs as init file, ignoring ~/.emacs.d/init.el"
>
> A warning prominent enough for people to notice would also be annoying
> enough that people would complain about us changing the status quo out
> from under them. The best we could do is putting something in
> *Messages*, I suspect
A line in *Messages* was what I was thinking of, yes. Maybe conditional
on a variable in case it turns out annoying for people who have shadowed
init files on purpose and want to keep their *Messages* buffer clean.
Or maybe a command `list-init-file-shadows' analogous to the existing
`list-load-path-shadows'.
next prev parent reply other threads:[~2021-07-07 16:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 22:56 bug#49424: 27.2; Misdocumented default initialisation file Peter Oliver
2021-07-06 15:11 ` Lars Ingebrigtsen
2021-07-07 9:17 ` Robert Pluim
2021-07-07 11:28 ` Rudolf Schlatte
2021-07-07 13:10 ` Robert Pluim
2021-07-07 16:33 ` Rudolf Schlatte [this message]
2021-07-07 12:24 ` Phil Sainty
2021-07-07 13:08 ` Robert Pluim
2021-07-07 14:11 ` Stephen Berman
2021-07-07 14:40 ` Robert Pluim
2021-07-07 16:21 ` Stephen Berman
2021-07-08 1:06 ` Phil Sainty
2021-07-07 17:58 ` Peter Oliver
2021-07-08 1:17 ` Phil Sainty
2021-07-08 7:23 ` Eli Zaretskii
2021-07-08 8:30 ` Robert Pluim
2021-07-08 9:21 ` Eli Zaretskii
2021-07-07 18:12 ` Peter Oliver
2021-07-07 18:36 ` Eli Zaretskii
2021-07-07 19:08 ` Peter Oliver
2021-07-07 19:27 ` Eli Zaretskii
2021-07-07 21:51 ` Peter Oliver
2021-07-08 6:23 ` Eli Zaretskii
2021-07-08 8:40 ` Robert Pluim
2021-07-08 9:22 ` Eli Zaretskii
2021-07-08 18:22 ` Peter Oliver
2021-07-08 19:10 ` Eli Zaretskii
2021-10-24 8:12 ` Stefan Kangas
2021-10-24 13:27 ` Lars Ingebrigtsen
2021-10-24 14:10 ` Stefan Kangas
2021-10-24 14:17 ` Lars Ingebrigtsen
2021-10-24 14:47 ` Stefan Kangas
2021-10-24 14:56 ` Stefan Kangas
2021-10-24 15:20 ` Eli Zaretskii
2021-10-24 21:52 ` Stefan Kangas
2021-10-24 14:25 ` Robert Pluim
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=m2v95mxew4.fsf@constantly.at \
--to=rudi@constantly.at \
--cc=49424@debbugs.gnu.org \
/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).