From: Yuri D'Elia <wavexx@thregr.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master a4144af 1/2: Prefer ~/.config/emacs to ~/.emacs.d if neither exists
Date: Fri, 30 Aug 2019 16:20:38 +0200 [thread overview]
Message-ID: <87h85ylop5.fsf@wavexx.thregr.org> (raw)
In-Reply-To: 83ftlial33.fsf@gnu.org
On Fri, Aug 30 2019, Eli Zaretskii wrote:
> We never discussed such a change, and I'm not sure I personally agree
> with it. XDG and its ~/.config directory is just one convention; why
> should we go after it by default, when there's no XDG setup visible
> anywhere in sight? Why should we force this convention on platforms
> other than GNU/Linux? That doesn't sound right to me.
I'd like to point out that this change also doesn't really work as
intended.
My expectation is that if ~/.config/emacs exists, it should be preferred
as it marks a clear indication that the user wants this path.
I'm fully ambivalent about the default if none exists.
Since I'd really like to follow XDG, I tried to move everything to
~/.config/emacs, but ~/.emacs.d is still created early during startup
anyway. This causes user-emacs-directory to be set to ~/.emacs.d. Even
manually setting user-emacs-directory in early-init doesn't prevent the
directory being created.
next prev parent reply other threads:[~2019-08-30 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 12:34 [Emacs-diffs] master a4144af 1/2: Prefer ~/.config/emacs to ~/.emacs.d if neither exists Eli Zaretskii
2019-08-30 14:20 ` Yuri D'Elia [this message]
2019-08-30 14:40 ` Eli Zaretskii
2019-09-01 6:25 ` Paul Eggert
2019-09-01 13:05 ` Stefan Monnier
2019-09-01 13:44 ` Teemu Likonen
2019-09-01 13:56 ` Eli Zaretskii
2019-09-02 19:03 ` Paul Eggert
[not found] <20190830072451.9819.83340@vcs0.savannah.gnu.org>
[not found] ` <20190830072452.ACB48210EC@vcs0.savannah.gnu.org>
2019-08-30 14:38 ` Stefan Monnier
2019-08-30 15:20 ` Kaushal Modi
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=87h85ylop5.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=emacs-devel@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 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.