[Date Prev][Date Next][Thread Prev][][Date Index][Thread Index]

Re: nnshimbun-request-scan fetches unsubscribed server groups

Katsumi Yamaoka <yamaoka@xxxxxxx> writes:

> In [emacs-w3m : No.11379] Matt Lundin wrote:
>> It works as expected (i.e., activates only subscribed groups at
>> startup) if I replace nnshimbun-request-group with
>> nnshimbun-request-scan in nnshimbun-retrieve-groups.
>> --- nnshimbun.el	2010-09-30 07:38:47.825664151 -0400
>> +++ nnshimbun-fix.el	2010-09-30 08:21:01.153141306 -0400
>> @@ -531,7 +531,7 @@
>>  (deffoo nnshimbun-retrieve-groups (groups &optional server)
>>    (when (nnshimbun-possibly-change-group nil server)
>>      (dolist (group groups)
>> -      (nnshimbun-request-group group server))
>> +      (nnshimbun-request-scan group server))
>>      t))
> Hmm, for me -group works but -scan doesn't.  Anyway I need to
> learn more how the most recent Gnus works...

You are right. With nnshimbun-request-scan, the groups are updated but
not displayed at startup (i.e., no data about the groups is provided to

On the other hand, with nnshimbun-request-group, the groups are
displayed but not updated.

I believe that nnshimbun-request-group only updates the nov database
(and article count) if the group is ephemeral and an .overview file does
not already exist (lines 510-513). Thus, both at startup and when
calling gnus-group-get-new-news, preexisting nnshimbun groups are not

Would it be possible to have nnshimbun-retrieve-groups call
nnshimbun-request-scan *and* nnshimbun-request-group in succession?