From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: Syncing Gnus
Date: Sun, 08 Jan 2012 01:40:25 +0100 [thread overview]
Message-ID: <qpsjjr2fie.fsf@news.eternal-september.org> (raw)
In-Reply-To: <94nw7go3m.fsf@news.eternal-september.org>
OK.. now I have the values set before gnus is loaded. Much better. And
most things seem to propery intitiate. However I *still* get a ~/Mail
created :-
,----
| [9096]shamrock@development:~$ ls -l Mail
| total 4
| drwxr-xr-x 2 shamrock shamrock 4096 Jan 8 01:29 archive
`----
My archive method is like this :-
,----
| (setq gnus-message-archive-method
| '(nnfolder "archive"
| (nnfolder-directory "~/Dropbox/.main/Mail/archive")
| (nnfolder-active-file "~/Dropbox/.main/Mail/archive/active")
| (nnfolder-get-new-mail nil)
| (nnfolder-inhibit-expiry t)))
`----
Is it not possible to lose the directory directives and have it based on the
other base settings? Am I missing a base setting (the nomenclature and
general Mail/News overlap makes it very hard to guess whats doinf what imo)
my setup pre load of gnus is now :-
,----
| (setq
| message-directory "~/Dropbox/.main/Mail/"
| ;; nndraft-directory "~/Dropbox/.main/News/drafts/"
| gnus-home-directory "~/Dropbox/.main/"
| ;; gnus-directory "~/Dropbox/.main/News/"
| ;; gnus-default-directory "~/Dropbox/.main/"
| ;; gnus-article-save-directory "~/Dropbox/.main/News/"
| ;; gnus-kill-files-directory "~/Dropbox/.main/News/"
| ;; gnus-cache-directory "~/Dropbox/.main/News/cache/"
| gnus-startup-file "~/.emacs.d/.newsrc"
| gnus-use-dribble-file nil
| bbdb-file "~/.emacs.d/.bbdb"
| nnfolder-directory "~/Dropbox/.main/Mail/archive"
| nnfolder-active-file "~/DropBox/.main/Mail/archive/active"
| )
`----
So, how to stop this "unnecessary" Mail dir being created?
next prev parent reply other threads:[~2012-01-08 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 21:51 Richard Riley
2012-01-07 22:11 ` Richard Riley
2012-01-08 0:40 ` Richard Riley [this message]
2012-01-08 1:40 ` Vitalie Spinu
2012-01-08 13:55 ` Sivaram Neelakantan
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=qpsjjr2fie.fsf@news.eternal-september.org \
--to=rileyrg@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).