Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: nndoc groups no longer inheriting parent parameters
Date: Sat, 26 Jan 2002 23:18:53 +0100	[thread overview]
Message-ID: <m3k7u4lprm.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m1bofjmt59x.fsf@blackbird.mitre.org>

david.goldberg6@verizon.net (David S. Goldberg) writes:

>> 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 nnvirtual groups ever have inherited other stuff than articles from
their component groups, that's something I haven't been aware of.

>> 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.

I'm unable to reproduce this bug.  If I put

((gnus-show-threads nil))

into the `G p' buffer, I get that variable set to nil in the group.
If I `C-d' a digest in that group, that variable is set to nil in that
nndoc group.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen



  reply	other threads:[~2002-01-26 22:18 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
2002-01-26 22:18             ` Lars Magne Ingebrigtsen [this message]
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=m3k7u4lprm.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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).