From: Matt Armstrong <matt@lickey.com>
Cc: ding@gnus.org
Subject: Re: No Gnus feature request: simpler file structure for synching
Date: Tue, 06 Jan 2004 23:22:24 -0800 [thread overview]
Message-ID: <873casgr4f.fsf@naz.lickey.com> (raw)
In-Reply-To: <uk7441u7e.fsf@ece.ucdavis.edu> (John Owens's message of "Tue, 06 Jan 2004 16:24:53 -0800")
John Owens <jowens@ucdavis.edu> writes:
> Unfortunately, the file structure for gnus is fairly complex. Kai
> points out that he synchs the following files to move state:
>
> "~/.newsrc*, ~/Mail/, ~/News/, ~/.nnmail-cache, and ~/.authinfo"
To solve similar problems, I have subdued Gnus into sticking all files
under my ~/g/ directory with the following in my .emacs:
----------------------------------------------------------------------
(setq
gnus-home-directory (expand-file-name "~/g/")
nnmail-message-id-cache-file (concat gnus-home-directory
".nnmail-cache")
mail-source-directory (concat gnus-home-directory "Mail/")
mail-source-crash-box (concat mail-source-directory
".emacs-mail-crash-box")
message-directory (concat gnus-home-directory "Mail/")
gnus-startup-file (concat gnus-home-directory ".newsrc"))
(setq-default gnus-init-file (expand-file-name "~/env/dot/gnus"))
And the following in my .gnus (which is actually ~/env/dot/gnus, see
above)
----------------------------------------------------------------------
(setq gnus-secondary-select-methods
'((nnml ""
(nnml-directory "/home/matt/g/nnml")
(nnml-active-file "/home/matt/g/nnml/active")
(nnml-newsgroupsfile "/home/matt/g/nnml/newsgroups"))))
I haven't figured out the lispy magic required to use "~/g/nnml"
etc. in the gnus-secondary-select-methods setq above.
--
matt (UCD grad)
next prev parent reply other threads:[~2004-01-07 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 0:24 No Gnus feature request: simpler file structure for synching between two machines John Owens
2004-01-07 7:22 ` Matt Armstrong [this message]
2004-01-07 8:27 ` No Gnus feature request: simpler file structure for synching Steve Youngs
2004-01-07 12:44 ` Kai Grossjohann
2004-01-07 14:28 ` Reiner Steib
2004-01-07 14:59 ` Kai Grossjohann
2004-01-07 17:42 ` nnir problems (was: No Gnus feature request: simpler file structure for synching) Reiner Steib
2004-01-07 16:20 ` No Gnus feature request: simpler file structure for synching Steven E. Harris
2004-01-08 22:23 ` Reiner Steib
2004-01-08 22:51 ` Steven E. Harris
2004-01-08 22:58 ` Paul Jarc
2004-01-07 17:07 ` John Owens
2004-01-07 17:47 ` Kai Grossjohann
2004-01-07 19:17 ` Josh Huber
2004-01-07 21:32 ` Simon Josefsson
2004-01-08 19:49 ` Steinar Bang
2004-01-11 21:49 ` Kai Grossjohann
2004-01-12 22:15 ` Steinar Bang
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=873casgr4f.fsf@naz.lickey.com \
--to=matt@lickey.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).