From: Eli Zaretskii <eliz@gnu.org>
To: Kelly Dean <kelly@prtime.org>
Cc: 19068@debbugs.gnu.org
Subject: bug#19068: Mail file vars aren't derived from customized message-directory
Date: Fri, 30 Jan 2015 11:06:58 +0200 [thread overview]
Message-ID: <83zj90ljrh.fsf@gnu.org> (raw)
In-Reply-To: <ZKbSgk3EKWpoFCRTA5qk9DTvLRixbLK1HxxvMgMTvSZ@local>
> From: Kelly Dean <kelly@prtime.org>
> CC: 19068@debbugs.gnu.org
> Date: Fri, 30 Jan 2015 07:11:52 +0000
>
> 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.
That's a separate issue. I'm not at all sure the user will always
want to rename all of them, but we could offer an option to do that.
next prev parent reply other threads:[~2015-01-30 9:06 UTC|newest]
Thread overview: 12+ 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
[not found] ` <4HEgHd24tKVHJkFYvKryLuxc8K21mIEO6gzZl9psynt@local>
2015-01-29 11:36 ` Ivan Shmakov
2015-01-29 16:09 ` Eli Zaretskii
2015-01-30 7:11 ` Kelly Dean
2015-01-30 7:35 ` Ivan Shmakov
2015-01-30 13:45 ` Ivan Shmakov
2015-01-30 9:06 ` Eli Zaretskii [this message]
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
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=83zj90ljrh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19068@debbugs.gnu.org \
--cc=kelly@prtime.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 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).