From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org,Robert Pluim <rpluim@gmail.com>
Cc: "Mingde (Matthew) Zeng" <matthewzmd@gmail.com>,
smartlitchi@gmail.com, "Elias Mårtenson" <lokedhs@gmail.com>
Subject: Re: Default emacs init file location confusion
Date: Wed, 08 Jan 2020 12:05:57 +0200 [thread overview]
Message-ID: <539DBEA2-E758-4CB0-B886-F908CF0525B6@gnu.org> (raw)
In-Reply-To: <m2eewajram.fsf@gmail.com>
On January 8, 2020 10:17:21 AM GMT+02:00, Robert Pluim <rpluim@gmail.com> wrote:
> >>>>> On Wed, 08 Jan 2020 09:22:12 +0200, Eli Zaretskii <eliz@gnu.org>
> said:
>
> Eli> Here's my proposal:
>
> Eli> . If neither the old nor the new (XDG compliant) directory
> exists, default to ~/.emacs.d (it will be created, as we did before)
> Eli> . If both the old and the new directory exist, use ~/.emacs.d
> Eli> . Otherwise use the XDG compliant directory
>
> Eli> This will make the new XDG compliant directory an opt-in feature:
> Eli> users who want that will have to create ~/.config/emacs, move
> there
> Eli> the contents of ~/.emacs.d, and then delete the latter, in order
> to
> Eli> have Emacs use the XDG convention.
>
> Except that now the issue becomes "I created ~/.config/emacs, and
> emacs doesnʼt use it".
Which is completely consistent with making this feature opt-in, don't you agree? And NEWS will tell so.
> hence Iʼd prefer:
>
> Use the XDG directory if it exists, but donʼt create
> it. Otherwise, use ~/.emacs.d (and create it if necessary).
This is IMO a much more invasive change, and therefore inappropriate for the release branch. The current code relies on user-emacs-directory to exist. Lifting this restriction should be a separate change, and we should do it on master.
> Eli> I don't like to pop up questions at startup, brcause users don't
> Eli> expect such questions, and because people who would like to keep
> their
> Eli> existing ~/.emacs.d and yet use ~/.config for other programs will
> need
> Eli> to respond to this prompt every time they start Emacs.
>
> I agree about the pop ups, but the prompt would only be if
> ~/.config/emacs existed, not ~/.config, so deleting it would stop the
> prompt.
The same people who won't know they should delete .emacs.d will also fail to know about deleting .config/emacs.
next prev parent reply other threads:[~2020-01-08 10:05 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 2:51 Default emacs init file location confusion Elias Mårtenson
2020-01-07 3:32 ` Eli Zaretskii
2020-01-07 3:40 ` Elias Mårtenson
2020-01-07 4:40 ` Eli Zaretskii
2020-01-07 14:43 ` Lawrence Liu
2020-01-07 15:26 ` Robert Pluim
2020-01-07 16:12 ` Eli Zaretskii
2020-01-07 16:25 ` Robert Pluim
2020-01-07 17:04 ` Eli Zaretskii
2020-01-07 17:11 ` Elias Mårtenson
2020-01-07 17:21 ` Eli Zaretskii
2020-01-07 17:33 ` Elias Mårtenson
2020-01-07 17:37 ` Eli Zaretskii
2020-01-08 5:28 ` Mingde (Matthew) Zeng
2020-01-08 5:33 ` Elias Mårtenson
2020-01-08 7:22 ` Eli Zaretskii
2020-01-08 10:05 ` Elias Mårtenson
[not found] ` <m2eewajram.fsf@gmail.com>
2020-01-08 10:05 ` Eli Zaretskii [this message]
2020-01-08 10:13 ` Elias Mårtenson
2020-01-08 10:22 ` Robert Pluim
2020-01-08 10:49 ` Eli Zaretskii
2020-01-08 12:37 ` Robert Pluim
2020-01-08 13:51 ` Stefan Monnier
2020-01-08 15:58 ` Eli Zaretskii
2020-01-08 16:28 ` Stefan Monnier
2020-01-08 16:32 ` Eli Zaretskii
2020-01-08 16:41 ` Mingde (Matthew) Zeng
2020-01-08 16:49 ` Robert Pluim
2020-01-08 17:01 ` Eli Zaretskii
2020-01-08 17:25 ` Robert Pluim
2020-01-08 17:35 ` Eli Zaretskii
2020-01-08 17:44 ` Robert Pluim
2020-01-08 17:56 ` Yuan Fu
2020-01-08 18:03 ` Robert Pluim
2020-01-09 2:27 ` Yuan Fu
2020-01-08 18:07 ` Eli Zaretskii
2020-01-08 18:12 ` Robert Pluim
2020-01-08 18:19 ` Eli Zaretskii
2020-01-08 19:45 ` Stefan Monnier
2020-01-08 20:03 ` Eli Zaretskii
2020-01-10 16:57 ` Eli Zaretskii
2020-01-11 1:46 ` Paul Eggert
2020-01-11 7:58 ` Eli Zaretskii
2020-01-11 15:43 ` Drew Adams
2020-01-11 16:16 ` Stefan Monnier
2020-01-11 18:08 ` Eli Zaretskii
2020-01-13 7:53 ` Robert Pluim
2020-01-13 14:36 ` Robert Pluim
2020-01-13 15:27 ` Colin Baxter
2020-01-13 15:37 ` Robert Pluim
2020-01-13 15:58 ` Colin Baxter
2020-01-13 16:05 ` Robert Pluim
2020-01-13 16:42 ` Eli Zaretskii
2020-01-13 16:59 ` Colin Baxter
2020-01-13 17:06 ` Robert Pluim
2020-01-13 17:21 ` Colin Baxter
2020-01-13 16:15 ` Eli Zaretskii
2020-01-13 16:39 ` Robert Pluim
2020-01-14 14:00 ` Robert Pluim
2020-01-14 16:05 ` Eli Zaretskii
2020-01-15 13:03 ` Robert Pluim
2020-01-15 17:32 ` Eli Zaretskii
2020-01-16 7:35 ` Robert Pluim
2020-01-16 15:02 ` Eli Zaretskii
2020-01-16 15:08 ` Robert Pluim
2020-01-13 16:52 ` Stefan Kangas
2020-01-13 16:17 ` Eli Zaretskii
2020-01-13 16:29 ` Robert Pluim
2020-01-08 23:26 ` chad
2020-01-08 23:32 ` Stefan Monnier
2020-01-09 3:34 ` Eli Zaretskii
2020-01-09 1:26 ` HaiJun Zhang
2020-01-09 5:07 ` 황병희
2020-01-08 11:03 ` Mario Lang
2020-01-08 15:56 ` Eli Zaretskii
2020-01-08 8:04 ` Robert Pluim
2020-01-07 17:57 ` Stefan Monnier
2020-01-07 18:08 ` Stefan Monnier
2020-01-07 18:09 ` Eli Zaretskii
2020-01-07 18:41 ` Stefan Monnier
2020-01-07 18:57 ` Yuan Fu
2020-01-07 19:15 ` Greg Farough
2020-01-07 20:11 ` Andrea Corallo
2020-01-07 18:53 ` Yuan Fu
2020-01-07 17:12 ` Yuan Fu
2020-01-07 17:26 ` Elias Mårtenson
2020-01-07 3:46 ` Mingde (Matthew) Zeng
2020-01-07 3:50 ` Elias Mårtenson
2020-01-07 3:43 ` VanL
2020-01-07 3:51 ` Elias Mårtenson
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=539DBEA2-E758-4CB0-B886-F908CF0525B6@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lokedhs@gmail.com \
--cc=matthewzmd@gmail.com \
--cc=rpluim@gmail.com \
--cc=smartlitchi@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.