From: Kelly Dean <kelly@prtime.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19068@debbugs.gnu.org
Subject: bug#19068: Mail file vars aren't derived from customized message-directory
Date: Fri, 30 Jan 2015 07:11:52 +0000 [thread overview]
Message-ID: <ZKbSgk3EKWpoFCRTA5qk9DTvLRixbLK1HxxvMgMTvSZ@local> (raw)
In-Reply-To: <83r3udmuvp.fsf@gnu.org>
Eli Zaretskii wrote:
>> Also,
>> grep -r "~/Mail/" emacs-24.4/lisp/ | grep 'el:'
>> gives 19 hits, all of which are inappropriate if ~/Mail isn't supposed to be hardcoded. If ~/Mail is supposed to be hardcoded, then the message-directory variable should be removed, to avoid misleading users.
>
> This is a red herring: all of these hits are either in comments or in
> default values of other defcustoms.
If a user renames his ⌜Mail⌝ directory to ⌜mail⌝, then he'll want all the things that previously used ⌜Mail⌝ to use ⌜mail⌝. Manually changing them all is tedious and error-prone, so it'd be nice to have one place to make the change. In Emacs, message-directory advertises itself as that place.
I lowercased my mail directory name both because it's easier to type that way (don't have to press shift), and because some other things already use the lowercase version by default, and there was no reason to use both upper- and lower-case versions.
next prev parent reply other threads:[~2015-01-30 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 11:27 bug#19068: Mail file vars aren't derived from customized message-directory Kelly Dean
2015-01-23 3:31 ` Kelly Dean
2015-01-28 10:17 ` bug#19068: [PATCH] " Kelly Dean
2015-01-29 8:27 ` bug#19068: " Lars Ingebrigtsen
2015-01-29 10:59 ` Kelly Dean
2015-01-29 11:36 ` Ivan Shmakov
2015-01-29 11:36 ` Ivan Shmakov
2015-01-29 16:09 ` Eli Zaretskii
2015-01-30 7:11 ` Kelly Dean [this message]
2015-01-30 7:35 ` Ivan Shmakov
2015-01-30 13:45 ` Ivan Shmakov
2015-01-30 9:06 ` Eli Zaretskii
2015-02-14 5:37 ` Lars Ingebrigtsen
2015-02-14 6:54 ` Ivan Shmakov
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=ZKbSgk3EKWpoFCRTA5qk9DTvLRixbLK1HxxvMgMTvSZ@local \
--to=kelly@prtime.org \
--cc=19068@debbugs.gnu.org \
--cc=eliz@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.