unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: ferkiwi@gmail.com, 583@debbugs.gnu.org
Subject: bug#583: Use XDG basedir spec for configuration files?
Date: Fri, 30 Aug 2019 12:18:40 -0400	[thread overview]
Message-ID: <ckimqeiq3j.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <499f2cba-39b3-afe1-7039-fb4c3cf73ea0@cs.ucla.edu> (Paul Eggert's message of "Fri, 30 Aug 2019 01:02:44 -0700")

Paul Eggert wrote:

>> BTW, I think the handling of user-emacs-directory is buggy:
>
> Yes, it is. I'll have to take a look at that. I guess we'll have to
> change user-home-directory to a variable, since we can't easily
> determine it until command-line runs.
>
> Also, a good many places in the documentaiton refer to ~/.emacs.d and
> these need to be updated.

IMO this means one should allow a user-defined user-emacs-directory,
which means un-wontfix'ing https://debbugs.gnu.org/15539 .
Maybe the patch in https://debbugs.gnu.org/15539#40 contains some useful ideas.
Although in hindsight an environment variable doesn't seem like the way
to go.





  reply	other threads:[~2019-08-30 16:18 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
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 [this message]
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=ckimqeiq3j.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=583@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=ferkiwi@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).