From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Deepak Negi <www.deepaknegilachu@gmail.com>,
66501@debbugs.gnu.org
Subject: bug#66501: 29.1; gnus-home-directory
Date: Thu, 12 Oct 2023 21:24:38 +0200 [thread overview]
Message-ID: <877cnriqyx.fsf@igel.home> (raw)
In-Reply-To: <CADwFkmkT7XtneGDmf2EtGUbXAkM=3CkiKSPYnUU=2DxTSvOtsQ@mail.gmail.com> (Stefan Kangas's message of "Thu, 12 Oct 2023 18:16:50 +0000")
On Okt 12 2023, Stefan Kangas wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> If that isn't sufficient, this is what I had to do in gnus-mock to make
>> sure absolutely all Gnus-related everything went in the same directory:
>>
>> (setq some-directory "~/.config/emacs/gnus"
>> gnus-home-directory some-directory
>> gnus-directory (expand-file-name "News/" some-directory)
>> message-directory some-directory
>> gnus-startup-file (expand-file-name ".newsrc" some-directory)
>> gnus-init-file (expand-file-name ".gnus.el" some-directory)
>> nndraft-directory (expand-file-name "drafts/" some-directory)
>> gnus-agent-directory (expand-file-name "agent/" some-directory))
>
> Is it really supposed to be this hard to customize?
No. Just setting gnus-home-directory is enough (though it needs to be
set before loading gnus).
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-10-12 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 15:20 bug#66501: 29.1; gnus-home-directory Deepak Negi
2023-10-12 16:46 ` Eric Abrahamsen
2023-10-12 18:16 ` Stefan Kangas
2023-10-12 19:24 ` Andreas Schwab [this message]
2023-10-12 22:10 ` Eric Abrahamsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cnriqyx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=66501@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=stefankangas@gmail.com \
--cc=www.deepaknegilachu@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).