From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: nndoc groups no longer inheriting parent parameters
Date: Tue, 22 Jan 2002 17:00:42 -0500 [thread overview]
Message-ID: <m1bofjmt59x.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <m3hepiw2kz.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 19 Jan 2002 20:41:32 +0100")
>>>>> On Sat, 19 Jan 2002 20:41:32 +0100, Lars Magne Ingebrigtsen
>>>>> <larsi@gnus.org> said:
> david.goldberg6@verizon.net (David S. Goldberg) writes:
>> Right. The nnvirutal group consists of comp.risks and
>> nnml:comp.risks. I the group parameters for both of those, I set
>> gnus-show-threads to nil. In the past, if I entered the nnvirtual
>> group and typed C-d on one of the digests (all messages are digests)
>> the digest would open with threading turned off. Now it does not.
> Right.
> Well, I think the current behavior is correct. nnvirtual groups
> should not inherit anything but the articles from the component
> groups.
Yes. I have no trouble with that change, other than I didn't see any
mention of it in the ChangeLog.
> If you want the nndoc group generated from the nnvirtual group to
> get `gnus-show-threads' set to nil, you have to add that parameter
> to the nnvirtual group.
But that's what I've done, and the nndoc group (which according to the
modeline is really a nnvirtual?!?!?) doesn't inherit the parameter.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2002-01-22 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 14:32 David S. Goldberg
2001-12-28 23:42 ` Lars Magne Ingebrigtsen
2001-12-31 15:07 ` David S. Goldberg
2001-12-31 22:22 ` Lars Magne Ingebrigtsen
2002-01-02 15:46 ` David S. Goldberg
2002-01-19 19:41 ` Lars Magne Ingebrigtsen
2002-01-22 22:00 ` David S. Goldberg [this message]
2002-01-26 22:18 ` Lars Magne Ingebrigtsen
2002-01-30 15:00 ` David S. Goldberg
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=m1bofjmt59x.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.net \
/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).