From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Cc: Gunnar Horrigmo <horrigmo@runbox.no>, Richard Stallman <rms@gnu.org>
Subject: Re: Cleaning up and structuring user-emacs-directory
Date: Wed, 19 Aug 2020 10:28:35 +0200 [thread overview]
Message-ID: <20200819082835.GA31976@tuxteam.de> (raw)
In-Reply-To: <87blj7jkg8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
On Wed, Aug 19, 2020 at 01:03:51AM -0400, Amin Bandali wrote:
> Richard Stallman writes:
>
> > [[[ To any NSA and FBI agents reading my email: please consider ]]]
> > [[[ whether defending the US Constitution against all enemies, ]]]
> > [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> >
> > > Would it not be better to follow the freedesktop spec?
> > > https://specifications.freedesktop.org/basedir-spec/basedir-spec-0.6.html
> >
> > Concretely, what change would that mean in Emacs?
>
> In short, the approach that I proposed divides up `user-emacs-directory'
> into multiple subdirectories and keeps `user-emacs-directory' as the
> all-in-one source of a user's Emacs files, while the XDG Base Directory
> approach as suggested by Gunnar would imply keeping only configuration
> files in `user-emacs-directory', and moving data and cache files to
> "$XDG_DATA_HOME/emacs/" and "$XDG_CACHE_HOME/emacs/" respectively, where
> 'XDG_DATA_HOME' defaults to "~/.local/share" and 'XDG_CACHE_HOME' to
> "~/.cache".
I've now read the freedesktop thing. If you ask me: please make that
optional. I have none of those $XDG_* env vars set, and I have nothing
of relevance in .local.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-08-19 8:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 19:30 A cache directory? Yuan Fu
2020-08-16 19:45 ` Yuri Khan
2020-08-16 20:43 ` Yuan Fu
2020-08-16 20:10 ` Cleaning up and structuring user-emacs-directory (was: A cache directory?) Amin Bandali
2020-08-18 4:06 ` Richard Stallman
2020-08-18 7:51 ` Cleaning up and structuring user-emacs-directory Gunnar Horrigmo
2020-08-18 22:41 ` Paul Eggert
2020-08-18 7:57 ` Gunnar Horrigmo
2020-08-19 4:01 ` Richard Stallman
2020-08-19 5:03 ` Amin Bandali
2020-08-19 8:28 ` tomas [this message]
2020-08-19 13:59 ` Amin Bandali
2020-08-19 14:18 ` tomas
2020-08-19 14:47 ` noah swainland
2020-08-19 14:42 ` David De La Harpe Golden
2020-08-19 16:14 ` tomas
2020-08-19 16:47 ` Yuan Fu
2020-08-19 17:33 ` Stefan Monnier
2020-08-19 18:39 ` Eli Zaretskii
2020-08-20 3:55 ` Stefan Monnier
2020-08-20 7:08 ` Andreas Schwab
2020-08-20 11:51 ` Stefan Monnier
2020-08-19 13:33 ` Stefan Monnier
2020-08-19 14:15 ` tomas
2020-08-20 3:09 ` Richard Stallman
2020-08-20 14:56 ` Yuan Fu
2020-08-20 15:24 ` Stefan Monnier
2020-08-20 17:14 ` T.V Raman
2020-08-21 3:33 ` Richard Stallman
2020-08-23 15:15 ` Stefan Monnier
2020-08-23 16:11 ` Stefan Kangas
2020-08-23 19:02 ` John Yates
2020-08-24 3:22 ` Richard Stallman
2020-08-21 9:49 ` Gunnar Horrigmo
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=20200819082835.GA31976@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
--cc=horrigmo@runbox.no \
--cc=rms@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.