From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org, npostavs@gmail.com, monnier@iro.umontreal.ca
Subject: Re: [PATCH] Implement XDG Base Directory specification for user-emacs-directory
Date: Mon, 10 Jun 2019 22:26:13 +0300 [thread overview]
Message-ID: <83lfy99r8q.fsf@gnu.org> (raw)
In-Reply-To: <m3ef41jlfu.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 10 Jun 2019 21:21:25 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>, Emacs developers <emacs-devel@gnu.org>
> Date: Mon, 10 Jun 2019 21:21:25 +0200
>
> Noam Postavsky <npostavs@gmail.com> writes:
>
> > Would it be okay to only use ~/.emacs.d as user-emacs-directory if
> > ~/.emacs.d/init.el exists?
>
> I've got an ~/.emacs.d directory where all the different Emacs packages
> store their data, but I don't have an ~/.emacs.d/init.el. Instead I
> have an ~/.emacs, and that's probably not an unusual configuration...
This is in fact identical to what I have here.
So maybe Stefan is right and we should unconditionally prefer ~/.emacs
and ~/.emacs.d to the XDG stuff, if the former exist.
next prev parent reply other threads:[~2019-06-10 19:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190525172356.30070.65317@vcs0.savannah.gnu.org>
[not found] ` <20190525172357.86D4F207F5@vcs0.savannah.gnu.org>
2019-05-26 22:40 ` [Emacs-diffs] master d68ed15: Implement and document XDG-style startup files under ~/.config Stefan Monnier
2019-06-03 2:32 ` Eli Zaretskii
2019-06-09 7:01 ` [PATCH] Implement XDG Base Directory specification for user-emacs-directory (was: [Emacs-diffs] master d68ed15: Implement and document XDG-style startup files under ~/.config.) Amin Bandali
2019-06-09 8:10 ` Eli Zaretskii
2019-06-09 18:59 ` [PATCH] Implement XDG Base Directory specification for user-emacs-directory Stefan Monnier
2019-06-09 19:16 ` Eli Zaretskii
2019-06-09 20:16 ` Noam Postavsky
2019-06-10 16:22 ` Eli Zaretskii
2019-06-10 18:55 ` Noam Postavsky
2019-06-10 19:21 ` Lars Ingebrigtsen
2019-06-10 19:26 ` Eli Zaretskii [this message]
2019-07-02 16:55 ` Noam Postavsky
2019-07-02 17:26 ` Eli Zaretskii
2019-07-23 14:36 ` Eli Zaretskii
2019-07-27 2:58 ` Amin Bandali
2019-07-27 7:55 ` Eli Zaretskii
2019-07-27 18:46 ` Paul Eggert
2019-07-27 21:22 ` Basil L. Contovounesios
2019-07-28 14:41 ` Eli Zaretskii
2019-07-28 15:21 ` Basil L. Contovounesios
2019-07-28 16:34 ` Eli Zaretskii
2019-07-28 14:48 ` Eli Zaretskii
2019-07-29 1:00 ` Elias Mårtenson
2019-07-29 2:36 ` Eli Zaretskii
2019-07-29 4:24 ` Elias Mårtenson
2019-07-29 14:21 ` Eli Zaretskii
2019-08-25 8:46 ` Eli Zaretskii
2019-08-27 21:50 ` Paul Eggert
2019-08-28 5:59 ` Eli Zaretskii
2019-06-13 11:34 ` [PATCH] Implement XDG Base Directory specification for user-emacs-directory (was: [Emacs-diffs] master d68ed15: Implement and document XDG-style startup files under ~/.config.) Stefan Kangas
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=83lfy99r8q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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 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).