all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kelly Dean <kelly@prtime.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug#19068: Mail file vars aren't derived from customized message-directory
Date: Thu, 29 Jan 2015 10:59:05 +0000	[thread overview]
Message-ID: <4HEgHd24tKVHJkFYvKryLuxc8K21mIEO6gzZl9psynt@local> (raw)
In-Reply-To: <871tme3sbm.fsf@building.gnus.org>

Lars Ingebrigtsen wrote:
> That's the wrong way to set variables that have other variables that
> depend on them.
>
> Instead say
>
> (setq message-directory "~/mail/")
> (require 'message)

And what if you happened to previously require something that already required message? Do you want to require users to always put all their «setq»s before all their «require»s, just in case?

Or what if you were already using message mode with the default directory settings, but then you decided to change it and customize message-directory using Emacs's customization feature, and read the help page that says ⌜Directory from which all other mail file variables are derived⌝? Would you not expect that when you change a top-level directory, the directories under it remain under it? After all, that's the way «mv» behaves.



  reply	other threads:[~2015-01-29 10:59 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 [this message]
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
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=4HEgHd24tKVHJkFYvKryLuxc8K21mIEO6gzZl9psynt@local \
    --to=kelly@prtime.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.