From: Pablo Sanchez <dev.null@blueoakdb.com>
To: info-gnus-english@gnu.org
Subject: Re: re-specifying ~/News and ~/Mail
Date: Mon, 11 Feb 2008 10:33:57 -0500 [thread overview]
Message-ID: <xp3arzjymy.fsf@dev.null.blueoakdb.com> (raw)
In-Reply-To: <mailman.7275.1202723861.18990.info-gnus-english@gnu.org>
Martin Geisler <mg@daimi.au.dk> writes:
> Pablo Sanchez <dev.null@blueoakdb.com> writes:
>
> Hi Pablo
Hi Martin,
> I think you want to change either this variable:
Once again, thank you for the information. It got me going in the
right direction. In order to affect this change, I had to make the
following changes:
(setq gnus-home-directory "~/.gnus.d")
(setq gnus-startup-file (concat gnus-home-directory ".newsrc"))
(setq gnus-cache-directory (concat gnus-home-directory "/cache"))
(setq message-directory (concat gnus-home-directory "/Mail"))
(setq gnus-directory (concat gnus-home-directory "/News"))
(setq gnus-agent-directory (concat gnus-directory "/agent"))
(setq message-auto-save-directory (concat message-directory "/drafts"))
By doing the above, all the gnus files and directories are placed in
~/gnus.d:
~/gnus.d/
.newsrc
Mail/
+--- drafts/
News/
+--- agent/
+--- drafts/
Now my top-level directory remains tidy. I suppose I should get to
work now. :p
Cheers,
--
pablo
next prev parent reply other threads:[~2008-02-11 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 13:28 Pablo Sanchez
2008-02-11 9:57 ` Martin Geisler
[not found] ` <mailman.7275.1202723861.18990.info-gnus-english@gnu.org>
2008-02-11 14:53 ` Pablo Sanchez
2008-02-12 7:17 ` Martin Geisler
2008-02-11 15:33 ` Pablo Sanchez [this message]
2008-02-12 7:20 ` Martin Geisler
[not found] ` <mailman.7324.1202801114.18990.info-gnus-english@gnu.org>
2008-02-12 13:46 ` Pablo Sanchez
2008-02-13 8:30 ` Martin Geisler
[not found] ` <mailman.7364.1202891426.18990.info-gnus-english@gnu.org>
2008-02-13 13:41 ` Pablo Sanchez
2008-02-14 11:08 ` anhnmncb
2008-02-14 20:01 ` Reiner Steib
2008-02-15 1:54 ` anhnmncb
2008-02-13 18:57 ` 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=xp3arzjymy.fsf@dev.null.blueoakdb.com \
--to=dev.null@blueoakdb.com \
--cc=info-gnus-english@gnu.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).