From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Subject: Re: Unnecessary nntp reading?
Date: 06 Jun 1997 11:06:28 +0200 [thread overview]
Message-ID: <tjg1uw6qy3.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 06 Jun 1997 05:12:01 +0200
>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> The activation level is orthogonal to the issue of reading the active
LMI> file.
OK. What does "activation level" mean? What does it do that
subscribedness levels don't do? Does it just control which lines in
the group buffer get updated?
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?
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.
[Guessing wildly] Or does activation level just prevent foreign groups
from being read? This I guess would be an advantage - if I have
foreign nntp groups on level 5 I may not want their servers to be read
but I may still want to read all of the groups on my primary server.
In any case, I think the documentation for gnus-activate-level (and
perhaps gnus-read-active-file) should explain better what it does.
And/or define activation level in the terminology section.
next prev parent reply other threads:[~1997-06-06 9:06 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 [this message]
1997-06-06 17:41 ` Lars Magne Ingebrigtsen
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=tjg1uw6qy3.fsf@sfs.nphil.uni-tuebingen.de \
--to=griffith@sfs.nphil.uni-tuebingen.de \
/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).