From: John H Palmieri <palmieri@math.washington.edu>
Subject: bug with drafts directory?
Date: Fri, 19 Apr 2002 13:26:53 -0700 [thread overview]
Message-ID: <s5tsn5rl9iq.fsf@goedel1.math.washington.edu> (raw)
I think there is a bug with nndraft-directory and
message-auto-save-directory. I want all my drafts to be stored in
"~/Mail/News/drafts", so I have this in my .emacs file:
(setq gnus-directory (expand-file-name "~/Mail/News")
gnus-kill-files-directory gnus-directory
gnus-dribble-directory gnus-directory
nndraft-directory gnus-directory)
The problem: with gnus running, when I create a draft (by running
gnus-group-mail, for instance, and then hitting C-c C-d), the
directory "~/Mail/drafts" is created. The draft is saved into the
right place, "~/Mail/News/drafts", though. I've fixed this by setting
the variable message-auto-save-directory to "~/Mail/News/drafts", but
I shouldn't have to: the documentation for that variable says
*Directory where Message auto-saves buffers if Gnus isn't running.
If nil, Message won't auto-save.
Note the clause "if Gnus isn't running".
Does anyone else get this behavior, or is something screwy with my
setup?
--
J. H. Palmieri, Dept of Mathematics, Univ of Washington
Gnus doesn't kill people, Emacs kills people.
reply other threads:[~2002-04-19 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=s5tsn5rl9iq.fsf@goedel1.math.washington.edu \
--to=palmieri@math.washington.edu \
/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.
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 NNTP newsgroup(s).