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 21:23:17 +0900 [thread overview]
Message-ID: <b4mtylsh5u1.fsf@jpl.org> (raw)
In-Reply-To: <m3iq28h6t6.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)) is always
>> true[1], so the previous code never used gnus-activate-group.
> No, nnvirtual doesn't have that one. :-) And the dont-subcheck thing
> in the last part is also for nnvirtual.
>> Whereas that seems to be the only means for nnrss groups to update.
>> Do you have an idea?
> The request-list thing is supposed to call request-scan, which is what
> nnrss needs. I haven't looked into why that doesn't happen, but I'll do
> so tonight.
Thanks in advance. Please note that nnrss-request-list always
makes a question to a user as Dave Goldberg pointed in:
http://article.gmane.org/gmane.emacs.gnus.general/70794
The gnus-group-get-new-news command didn't call it before.
next prev parent reply other threads:[~2010-09-14 12:23 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
2010-09-14 12:02 ` Lars Magne Ingebrigtsen
2010-09-14 12:03 ` Lars Magne Ingebrigtsen
2010-09-14 12:23 ` Katsumi Yamaoka [this message]
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=b4mtylsh5u1.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).