From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master a4144af 1/2: Prefer ~/.config/emacs to ~/.emacs.d if neither exists
Date: Sat, 31 Aug 2019 23:25:26 -0700 [thread overview]
Message-ID: <44c7794c-29a7-65be-0838-f84807eba9bc@cs.ucla.edu> (raw)
In-Reply-To: <83ftlial33.fsf@gnu.org>
Eli Zaretskii wrote:
> Why should we force this convention on platforms other than GNU/Linux?
We're not forcing the new convention on any platform, as people who prefer the
old convention can still use it and Emacs will continue to respect that
convention on all platforms. That is, users who prefer the old convention won't
need to do anything special to their home directories that use the old
convention; they can just run Emacs as before and it will work as before.
The issue came up when I was testing a fix for the bug Glenn reported
<https://bugs.gnu.org/583#56>. There are four cases when Emacs starts up:
(1) only ~/.config/emacs (the new-convention directory) is present, where Emacs
obviously should use that;
(2) only ~/.emacs.d (the old-convention directory) is present, where Emacs
obviously should use that;
(3) both directories are present, where I recall that we discussed that Emacs
should use the new-convention directory; and
(4) neither directory is present, which we did not discuss explicitly but I
reasoned by analogy with (3) that Emacs should also prefer the new convention
when either the old or the new will do.
It would be quite odd if case (4) were done the opposite way, because then Emacs
would prefer the new convention for case (3) and the old convention for case
(4), and this mixup would likely cause more confusion than it would cure.
Whatever we decide about case (4) should be independent of platform, since some
users move config files between GNUish and non-GNUish platforms or share these
files via network protocols or run Emacs on both GNUish and non-GNUish
platforms, and it would cause unnecessary trouble for users if Emacs behaved
differently on GNU/Linux versus other platforms.
next prev parent reply other threads:[~2019-09-01 6:25 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
2019-08-30 14:40 ` Eli Zaretskii
2019-09-01 6:25 ` Paul Eggert [this message]
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=44c7794c-29a7-65be-0838-f84807eba9bc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.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.