From: anhnmncb <anhnmncb@sina.com>
To: info-gnus-english@gnu.org
Subject: Re: Mail/drafts is still at ~/
Date: Sat, 01 Mar 2008 18:32:50 +0800 [thread overview]
Message-ID: <86prueg2el.fsf@freebsd.hasee.cpu> (raw)
In-Reply-To: <v94pbvmtlf.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Tue, Feb 26 2008, anhnmncb wrote:
>
>> After setting:
>> (setq gnus-home-directory "~/.emacs.d/gnus")
>> (setq message-directory (concat gnus-home-directory "/Mail"))
>> Everything goes well except that when I postpone a mail, drafts will go
>> into ~/Mail/drafts, not the expecting ~/.emacs.d/gnus/Mail/drafts.
>
> The relevant variable `nndraft-directory' is correctly derived from
> `gnus-directory':
>
> (defvoo nndraft-directory (nnheader-concat gnus-directory "drafts/")
> "Where nndraft will store its files."
>
> It seems to work correctly for me:
>
> ,----[ emacs -Q -f ielm ]
> | *** Welcome to IELM *** Type (describe-mode) for help.
> | ELISP> (setq gnus-home-directory "~/.emacs.d/gnus")
> | "~/.emacs.d/gnus"
> | ELISP> (setq message-directory (concat gnus-home-directory "/Mail"))
> | "~/.emacs.d/gnus/Mail"
> | ELISP> (require 'nndraft)
> | nndraft
> | ELISP> nndraft-directory
> | "~/.emacs.d/gnus/News/drafts/"
> `----
>
> Maybe for you loaded `nndraft.el' before setting those variables?
>
> Bye, Reiner.
Hi, reiner, seems the variable is right, but ~/Mail/drafts still
appears, though it's empty, don't know why.
I've testied after rm -r ~/Mail several times.
------
nndraft-directory is a variable defined in `nndraft.el'.
Its value is
"~/.emacs.d/gnus/News/drafts/"
------
--
Regards,
anhnmncb
gpg key: 44A31344
prev parent reply other threads:[~2008-03-01 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 11:08 anhnmncb
2008-02-26 18:59 ` Reiner Steib
2008-02-26 23:46 ` anhnmncb
2008-02-27 0:48 ` Katsumi Yamaoka
2008-02-27 3:58 ` anhnmncb
2008-02-27 4:28 ` anhnmncb
2008-02-27 6:54 ` Katsumi Yamaoka
2008-03-01 10:32 ` anhnmncb [this message]
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=86prueg2el.fsf@freebsd.hasee.cpu \
--to=anhnmncb@sina.com \
--cc=info-gnus-english@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.
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).