Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Unnecessary nntp reading?
Date: 06 Jun 1997 19:41:40 +0200	[thread overview]
Message-ID: <m2u3jbhbmz.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: John Griffith's message of 06 Jun 1997 11:06:28 +0200

John Griffith <griffith@sfs.nphil.uni-tuebingen.de> writes:

> OK.  What does "activation level" mean?

It means that Gnus does the math to figure out how many unread
articles there are in groups.  Unactivated groups are listed with "*"
in the group buffer.

> What does it do that subscribedness levels don't do?  Does it just
> control which lines in the group buffer get updated?

Yes.

> I haven't tried this, but does it mean that if my activation level say
> 2 and I have nntp groups on level 3 and gnus-read-active-file is
> `some' (and level 3 is a subscribed level - or even an unsubscribed
> level) then all the active file information will be retrieved but it
> just won't be shown?

Yes.

> If so, then what is the purpose of activation level?  If I don't want
> to see the level 3 groups I can just look at the level 2 and below
> groups.

Yes, that's true.

The activation level is mostly irrelevant -- unless you have set
`gnus-read-active-file' to nil.  In which case it is relevant.

> [Guessing wildly] Or does activation level just prevent foreign groups
> from being read?

No, that's controlled by `gnus-activate-foreign-newsgroups'.

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


      reply	other threads:[~1997-06-06 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-31 10:14 John Griffith
1997-06-06  3:12 ` Lars Magne Ingebrigtsen
1997-06-06  9:06   ` John Griffith
1997-06-06 17:41     ` Lars Magne Ingebrigtsen [this message]

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=m2u3jbhbmz.fsf@proletcult.slip.ifi.uio.no \
    --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).