From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: horrigmo@runbox.no, casouri@gmail.com, bandali@gnu.org,
emacs-devel@gnu.org
Subject: Re: Cleaning up and structuring user-emacs-directory
Date: Thu, 20 Aug 2020 23:33:21 -0400 [thread overview]
Message-ID: <E1k8xnt-0004S7-8V@fencepost.gnu.org> (raw)
In-Reply-To: <jwva6ypxrw1.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 20 Aug 2020 11:24:11 -0400)
[[[ 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. ]]]
The doc string of ecomplete-database-file suggests that the file is
really a kind of cache. Is that so? Would deleting the file be
harmless?
I have a feeling that recentf-save-file is also a cache file. Is that so?
On the other hand, it looks like bookmark-default-file is a file of
user data, and deleting the file would lose the user's data. Is that
so?
It is not unreasonable to store the data files in a separate directory
from configuration files. However, if there are few of them it is not
worth the trouble to separate them.
We should take care to distinguish which files are cache files
and put them into ~/.cache.
It makes sense to put data files like that one into a separate place
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-08-21 3:33 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
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 [this message]
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=E1k8xnt-0004S7-8V@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bandali@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=horrigmo@runbox.no \
--cc=monnier@iro.umontreal.ca \
/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.