From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: ferkiwi+a@gmail.com, eggert@cs.ucla.edu, 583@debbugs.gnu.org
Subject: bug#583: Use XDG basedir spec for configuration files?
Date: Thu, 29 Aug 2019 10:03:53 +0300 [thread overview]
Message-ID: <83mufsbgh2.fsf@gnu.org> (raw)
In-Reply-To: <sn8srczpd8.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 28 Aug 2019 22:17:55 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: 583@debbugs.gnu.org, ferkiwi+a@gmail.com, eggert@cs.ucla.edu
> Date: Wed, 28 Aug 2019 22:17:55 -0400
>
> IMO a true conversion of Emacs to the XDG spec would involve the
> addition of new variables (user-config-directory, user-data-directory,
> user-cache-directory, etc). Each use of user-emacs-directory would have
> to be reviewed to see where it actually belongs. For some, it would
> probably be ambiguous.
I'm afraid almost all of them will be ambiguous. Moreover, defining a
clear enough set of rules for where to put files that will be added in
the future is a non-trivial job, and enforcing it will not be easy. I
predict confusion and arguments.
My gut feeling is that Emacs should have one, at most 2 XDG-derived
directories, certainly not 3. And if we want to support that
correctly, these environment variables should be accessed much earlier
in the startup process, somewhere in init_callproc and friends,
because setting user-emacs-directory in startup is too late and
creates problems, as we saw already.
We've made a small step in that direction; if we want to continue that
way, someone should volunteer to do the job of defining what files
will go were.
next prev parent reply other threads:[~2019-08-29 7:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 6:59 bug#583: Use XDG basedir spec for configuration files? Fernando
2012-12-08 12:18 ` bug#583: XDG basedir specification Eric Heintzmann
2012-12-08 19:06 ` Jan Djärv
2012-12-08 19:31 ` Eli Zaretskii
2019-08-27 21:57 ` bug#583: Use XDG basedir spec for configuration files? Paul Eggert
2019-08-28 16:11 ` Glenn Morris
2019-08-28 16:29 ` Eli Zaretskii
2019-08-28 16:50 ` Glenn Morris
2019-08-28 17:18 ` Eli Zaretskii
2019-08-29 2:17 ` Glenn Morris
2019-08-29 7:03 ` Eli Zaretskii [this message]
2019-08-28 18:11 ` Paul Eggert
2019-08-29 2:14 ` Glenn Morris
2019-08-29 6:22 ` Paul Eggert
2019-08-29 8:42 ` Štěpán Němec
2019-08-29 18:30 ` Glenn Morris
2019-08-29 18:35 ` Glenn Morris
2019-08-29 18:53 ` Eli Zaretskii
2019-08-30 8:02 ` Paul Eggert
2019-08-30 16:18 ` Glenn Morris
2019-08-30 17:44 ` Eli Zaretskii
2019-09-01 1:56 ` bug#15539: [PATCH] Setting user-emacs-directory Paul Eggert
2019-09-02 23:45 ` Glenn Morris
2019-09-03 6:29 ` Paul Eggert
2019-09-08 14:54 ` Mike Carifio
2020-08-13 11:06 ` Lars Ingebrigtsen
2019-09-01 2:02 ` bug#583: Use XDG basedir spec for configuration files? Paul Eggert
2019-09-01 14:38 ` Eli Zaretskii
2019-09-01 18:40 ` Paul Eggert
2019-09-01 18:50 ` Eli Zaretskii
2019-09-01 23:01 ` Paul Eggert
2019-08-31 21:51 ` Paul Eggert
2019-09-11 9:21 ` Sven Joachim
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=83mufsbgh2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=583@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=ferkiwi+a@gmail.com \
--cc=rgm@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).