From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: Juanma Barranquero <lekktu@gmail.com>,
4347@emacsbugs.donarmstrong.com, Emacs <emacs-devel@gnu.org>
Subject: Re: bug#4347: Bug for .emacs.d?
Date: Sat, 12 Sep 2009 15:32:31 -0400 [thread overview]
Message-ID: <jwvbplgj74h.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <4AAB5BD0.2010503@alice.it> (Angelo Graziosi's message of "Sat, 12 Sep 2009 10:29:04 +0200")
>> There's no question that the behavior changed. And clearly you do not
>> like it. But ... what's the harm?
>> Lots of programs create a ~/.foo directory at start.
> Just a question: is the creation of this empty directory (~/.emacs.d) the
> result of a design in the code for the next Emacs 23.2 or is it a unexpected
> result of that code?
It's not on-purpose, no. It's not exactly unexpected, tho. The issue
is pretty simple: Emacs packages often can use either ~/.<foo> (old
style) or ~/.emacs.d/<foo> (new style) files to store some customization
or state.
If neither of the two files exist, we prefer to use ~/.emacs.d/<foo>,
but at the time we make this choice, we usually don't know yet whether
the file will be written, and at the time the file is written, we
generally assume that the parent directory already exists.
So the ~/.emacs.d directory is created eagerly.
In other words, this behavior is clearly not a feature, but "fixing" it
is somewhat of a pain for very little gain.
Stefan
next prev parent reply other threads:[~2009-09-12 19:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 0:27 Bug for .emacs.d? Angelo Graziosi
2009-09-05 2:12 ` bug#4347: " Juanma Barranquero
2009-09-11 20:23 ` Stefan Monnier
2009-09-11 20:34 ` Juanma Barranquero
2009-09-11 21:21 ` Angelo Graziosi
2009-09-12 4:25 ` Stefan Monnier
2009-09-12 8:29 ` Angelo Graziosi
2009-09-12 8:29 ` Angelo Graziosi
2009-09-12 19:32 ` Stefan Monnier
2009-09-12 19:32 ` Stefan Monnier [this message]
2009-09-12 21:43 ` Angelo Graziosi
2009-09-13 2:31 ` Miles Bader
2009-09-13 2:31 ` Miles Bader
2009-09-13 2:57 ` message creates ~/Mail [was Re: bug#4347: Bug for .emacs.d?] Glenn Morris
2009-09-13 3:23 ` message creates ~/Mail Miles Bader
2009-09-13 8:20 ` Reiner Steib
2009-09-13 8:56 ` Miles Bader
2009-09-13 11:12 ` Daniel Clemente
2009-09-14 19:07 ` Glenn Morris
2009-09-13 4:16 ` Stefan Monnier
2009-09-12 21:43 ` bug#4347: Bug for .emacs.d? Angelo Graziosi
2009-09-13 13:06 ` Angelo Graziosi
2009-09-13 13:06 ` Angelo Graziosi
2009-09-13 13:35 ` Juanma Barranquero
2009-09-13 13:48 ` Angelo Graziosi
2009-09-13 13:48 ` Angelo Graziosi
2009-09-13 13:35 ` Juanma Barranquero
2009-09-13 14:04 ` Stefan Monnier
2009-09-13 14:04 ` Stefan Monnier
2009-09-13 14:12 ` Angelo Graziosi
2009-09-13 17:41 ` Juanma Barranquero
2009-09-13 17:41 ` Juanma Barranquero
2009-09-13 14:12 ` Angelo Graziosi
2009-09-13 16:06 ` desktop and ~/.emacs.d/ (was: bug#4347: Bug for .emacs.d?) Reiner Steib
2009-09-14 1:26 ` desktop and ~/.emacs.d/ Stefan Monnier
2009-09-14 1:30 ` Juanma Barranquero
2009-09-14 14:22 ` Davis Herring
2009-09-14 14:43 ` Lennart Borgman
2009-09-14 15:17 ` Davis Herring
2009-09-12 11:16 ` bug#4347: Bug for .emacs.d? Juanma Barranquero
2009-09-12 19:38 ` Stefan Monnier
2009-09-12 19:42 ` Juanma Barranquero
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=jwvbplgj74h.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4347@emacsbugs.donarmstrong.com \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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 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.