From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: gnus-start.el (gnus-read-active-for-groups): Run gnus-activate-group for back end that doesn't support request-scan.
Date: Tue, 14 Sep 2010 20:45:58 +0900 [thread overview]
Message-ID: <b4my6b4h7k9.fsf@jpl.org> (raw)
In-Reply-To: <m38w34ljhe.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> > - ((gnus-check-backend-function 'request-list (car method))
> > + ((gnus-check-backend-function 'request-scan (car method))
> > (gnus-read-active-file-1 method nil infos))
> > (t
> > (dolist (info infos)
> > - (gnus-activate-group (gnus-info-group info) nil nil method t))))))
> > + (gnus-activate-group (gnus-info-group info) nil nil method))))))
> No, that can't be right. Now you're running lock-step group activation
> on all backends that don't support request-scan, like nntp, instead of
> issuing nntp-request-list.
(gnus-check-backend-function 'request-list (car method)) is always
true[1], so the previous code never used gnus-activate-group.
Whereas that seems to be the only means for nnrss groups to update.
Do you have an idea?
[1] (info "(gnus)Required Back End Functions")
next prev parent reply other threads:[~2010-09-14 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OvMLQ-0001BW-00@quimby.gnus.org>
2010-09-14 10:14 ` Lars Magne Ingebrigtsen
2010-09-14 11:45 ` Katsumi Yamaoka [this message]
2010-09-14 12:02 ` Lars Magne Ingebrigtsen
2010-09-14 12:03 ` Lars Magne Ingebrigtsen
2010-09-14 12:23 ` Katsumi Yamaoka
2010-09-14 12:28 ` Lars Magne Ingebrigtsen
2010-09-14 12:37 ` 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=b4my6b4h7k9.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).