From: Dave Abrahams <dave@boostpro.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org
Subject: Re: Where are group parameters stored?
Date: Tue, 12 Jul 2011 13:21:29 -0400 [thread overview]
Message-ID: <m2hb6r4dpi.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <8762ncnb5a.fsf@member.fsf.org> (Tassilo Horn's message of "Fri, 08 Jul 2011 15:40:33 +0200")
on Fri Jul 08 2011, Tassilo Horn <tassilo-AT-member.fsf.org> wrote:
> Dave Abrahams <dave@boostpro.com> writes:
>
> Hi Dave,
>
>> I can't figure out where Gnus is putting them.
>
> Well, you can specify them in your ~/.gnus.el using `gnus-parameters',
> and then they are exactly there. ;-)
>
> If you specify them using `G c' or `G p' on a group, then I think they
> go in ~/.newsrc.eld, but I might be wrong.
Okay, that seems problematic. Shouldn't everything you specify with `G
c' or `G p' be stored as a regular customization? IIUC, .newsrc.eld
changes very dynamically (e.g. storing article marks), whereas group
parameters are the sort of thing I'd probably want to check into a Git
repository somewhere. Am I missing something?
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-07-12 17:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:31 Dave Abrahams
2011-07-08 13:40 ` Tassilo Horn
2011-07-12 17:21 ` Dave Abrahams [this message]
2011-07-12 18:26 ` Tassilo Horn
2011-07-13 0:54 ` lee
2011-07-13 7:13 ` Tassilo Horn
2011-07-13 20:05 ` lee
2011-07-13 20:50 ` inheritatively specifying group parameters (was: Where are group parameters stored?) lee
2011-07-13 21:18 ` inheritatively specifying group parameters Peter Münster
2011-07-14 6:16 ` Tassilo Horn
2011-07-14 16:05 ` lee
2011-07-14 6:19 ` Where are group parameters stored? Tassilo Horn
2011-07-14 16:25 ` lee
2011-07-14 18:26 ` Tassilo Horn
2011-07-14 19:18 ` lee
2011-07-14 17:20 ` Dave Abrahams
2011-07-13 5:23 ` Steinar Bang
2011-07-19 16:49 ` Lars Magne Ingebrigtsen
2011-07-13 5:18 ` 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=m2hb6r4dpi.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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).