From: Vitalie Spinu <spinuvit.list@gmail.com>
To: ding@gnus.org
Subject: Re: Syncing Gnus
Date: Sun, 08 Jan 2012 02:40:16 +0100 [thread overview]
Message-ID: <87vconc6pr.fsf@gmail.com> (raw)
In-Reply-To: <qpsjjr2fie.fsf@news.eternal-september.org> (Richard Riley's message of "Sun, 08 Jan 2012 01:40:25 +0100")
Richard Riley <rileyrg@gmail.com> writes:
> 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)))
> `----
Hi Richard,
I struggled with the exactly the same problem when synchronizing
Dropbox. I was sloppy enough in my comments
/===
| ;; (setq gnus-update-message-archive-method t) ;; doesn't seem to work
| as advertised, edit gnus.eld directly to have an effect
\===
In the documentation of gnus-update-message-archive-method is stated
that gnus.eld should be updated automatically, but it is not.
So, I just replaced manually all the occurrences of ~/Mail/archive in gnus.eld
with ~/Dropbox/.main/Mail/archive .
The main problem is that not all of gnus dirs are set from
gnus-directory as claimed in the docs (for instance
gnus-article-save-directory gnus-kill-files-directory and
gnus-cache-directory).
The nuisance with Mail/archive was really confusing. It took me ages to
figure it out. It would be nice if someone could simplify it a bit.
Best,
Vitalie.
next prev parent reply other threads:[~2012-01-08 1: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
2012-01-08 1:40 ` Vitalie Spinu [this message]
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=87vconc6pr.fsf@gmail.com \
--to=spinuvit.list@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).