From: David <de_bb@arcor.de>
To: ding@gnus.org
Subject: What does gnus-group-get-new-news do with arg=nil?
Date: Tue, 03 Jun 2008 16:55:10 +0200 [thread overview]
Message-ID: <kzskvu601d.fsf@kafka.physik3.gwdg.de> (raw)
I tried to figure out what gnus-group-get-new-news actually does without
further arguments and with permanent levels unset, and I simply don't
get it. Please also note that the doc-string carefully avoids this
question. My impression was that gnus-activate-level would be used, but
it doesn't seem to be that easy.
The question boils down to what gnus-get-unread-articles does without
arguments, i.e. level=nil. What I'd like in this case is that every
group with a level greater than gnus-activate-level should be completely
ignored, but this doesn't happen. If level is nil, 'active' is never set
to 'ignore in the following code:
(if (and level
;; If `active' is nil that means the group has
;; never been read, the group should be marked
;; as having never been checked (see below).
active
(> (gnus-info-level info) level))
;; Don't check groups of which levels are higher
;; than the one that a user specified.
(setq active 'ignore))))
Therefore, later in the code, gnus-get-unread-articles-in-group is
called, even for foreign groups with a level greater than gnus-activate-group:
(cond
((eq active 'ignore)
;; Don't do anything.
)
(active
(inline (gnus-get-unread-articles-in-group info active t)))
Is this really the wanted behavior? It seems unnecessary to me - if I
just hit 'g' without a prefix, I think everything greater than
gnus-activate-level shouldn't be touched at all.
-David
next reply other threads:[~2008-06-03 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 14:55 David [this message]
2008-06-06 7:20 ` Katsumi Yamaoka
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=kzskvu601d.fsf@kafka.physik3.gwdg.de \
--to=de_bb@arcor.de \
--cc=ding@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).