From: jorge.a.alfaro@gmail.com (Jorge A. Alfaro-Murillo)
To: ding@gnus.org
Subject: Re: nndraft directory
Date: Fri, 30 May 2014 14:17:53 -0400 [thread overview]
Message-ID: <87r43bdtbi.fsf@gmail.com> (raw)
In-Reply-To: <m3mwe8tizy.fsf@neo.luffy.cx>
Hi Vincent.
Vincent Bernat <bernat@luffy.cx> writes:
> Despite removing it multiple times, the directory `~/Mail/drafts` keep
> being recreated by Gnus. `nndraft-directory` is set to
> `/home/bernat/.emacs.d/run/gnus/drafts/`. What could recreate the
> directory?
I had a similar issue recently. I wanted to move the Mail and News
directories to another location. I did not have your problem exactly,
probably because I use nntp as my gnus-select-method and the nnimap's as
gnus-secondary-select-methods. But ~/Mail/archive kept being created
even after changing nnfolder-active-file and it was driving me crazy.
The documentation of the variable that you mention and of
nnfolder-active-file mention that they are "Gnus server variables". I
understood after reading (info "(gnus) Server Variables") that for my
case I could not set it simply with a setq, this was needed:
#+BEGIN_SRC emacs-lisp
(setq message-directory "~/path_that_I_wanted/Mail/")
(setq gnus-message-archive-method
'(nnfolder "archive"
(nnfolder-directory
"~/path_that_I_wanted/Mail/archive/")
(nnfolder-active-file
"~/path_that_I_wanted/Mail/archive/active")
(nnfolder-inhibit-expiry t)))
(setq gnus-update-message-archive-method t)
#+END_SRC
For your case probably you have to explicitly set all the variables from
the nndraft group in a similar way. Perhaps someone can clarify server
variables further.
Best,
Jorge.
next prev parent reply other threads:[~2014-05-30 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 19:03 Vincent Bernat
2014-05-23 19:09 ` Rasmus
2014-05-23 20:51 ` Vincent Bernat
2014-05-30 18:17 ` Jorge A. Alfaro-Murillo [this message]
2014-05-30 22:46 ` Vincent Bernat
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 17:52 Richard Riley
2011-01-19 21:31 ` Richard Riley
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=87r43bdtbi.fsf@gmail.com \
--to=jorge.a.alfaro@gmail.com \
--cc=ding@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.
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).