Gnus development mailing list
 help / color / mirror / Atom feed
From: Tony Lam <Tony.Lam+ding@eng.sun.com>
Subject: Re: Groups no longer active
Date: 31 Aug 1999 14:19:39 -0700	[thread overview]
Message-ID: <4jy1zcj8ytw.fsf@homeworld.Eng.Sun.Com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1999 19:13:00 +0200"

* "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

Lars> Tony Lam <Tony.Lam+ding@Eng.Sun.Com> writes:
>> This new behavior seems make sense, but I think when I do "M-g" on
>> topics it should still active all subscribed groups under the topics,
>> and fetch all news messages in the groups. I shouldn't have to do "M-g
>> 3" to activate *all* groups on level 3 and below just to read a few
>> groups in a topic.

Lars> Hm.  I've looked over the code, and I can't see anything there that
Lars> considers group levels.

When I start Gnus with 'M 2 M-x gnus', PGnus completely ignores all
groups at level >2 in gnus-get-unread-articles, i.e. does not store
them in active hash table, while in Gnus 5.6.45, the same function put
all groups in active hash table, and set groups at >2 to inactive. It
looks like that's why doing 'M-g' on topic later in PGnus doesn't get
any subscribed groups at level 2+ but works fine in Gnus 5.6.45.

There seems a reason for Gnus to change to the new behavior, but how
can I get all subscribed groups under a topic without activating all
groups from all servers?

Lars> Does `T #' only mark the groups that are on the specified level?

Yes.

Thanks in advance for any help.

Tony


  reply	other threads:[~1999-08-31 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-11  0:33 Tony Lam
1999-08-27 17:13 ` Lars Magne Ingebrigtsen
1999-08-31 21:19   ` Tony Lam [this message]
1999-09-25  7:48     ` Lars Magne Ingebrigtsen
1999-09-27 19:52       ` Tony Lam
1999-09-27 21:04         ` Lars Magne Ingebrigtsen
1999-09-27 21:08           ` Tony Lam
1999-11-19  1:34           ` Tony Lam

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=4jy1zcj8ytw.fsf@homeworld.Eng.Sun.Com \
    --to=tony.lam+ding@eng.sun.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.
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).