From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: [Q]: ~/Mail directory
Date: Wed, 11 Feb 2004 23:06:21 +0100 [thread overview]
Message-ID: <plop874qtxcluq.fsf@gnu-rox.org> (raw)
In-Reply-To: <87bro6kjku.fsf@katrine.aae.uiuc.edu> (D. Michael McFarland's message of "Tue, 10 Feb 2004 10:03:45 -0600")
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On 10 Feb 2004, D. Michael McFarland said:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
> > Setting `gnus-directory' and `message-directory' should be enough.
>
> Apologies for jumping into the middle of this thread, but I expect one
> of the resident experts here can save me from shooting myself in the
> foot.
>
> If I create the directories `~/.gnus.d' and `~/message.d' and set
> `gnus-directory' and `message-directory' to them, gnus is happy but,
> naturally, some state information is not found. I know I need to move
> some gnus- and message-specific files from ~/News and ~/Mail to the
> new directories, but I'm not sure exactly which. cache, agent,
> drafts? *.SCORE? Others? Or should I just leave well enough alone?
> I'd like to move the gnusish bits out of ~/News and ~/Mail, but I
> can't really claim to have a burning need to do so. I'd appreciate
> recommendations from those who know about the magic gnus does behind
> the scenes.
Give a try to my setup posted above.
zeDek
--
.o. | Hacker wonderland
..o |
ooo |
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-02-11 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 8:12 Xavier Maillard
2004-02-09 20:41 ` Mark Plaksin
2004-02-10 6:35 ` Xavier Maillard
2004-02-10 13:28 ` Reiner Steib
2004-02-10 16:03 ` D. Michael McFarland
2004-02-11 22:06 ` Xavier Maillard [this message]
2004-07-18 23:58 ` Andrew J. Korty
2004-07-19 11:01 ` Reiner Steib
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=plop874qtxcluq.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).