Re: Semi-automatical update of article count in nnfolder?

[kai.grossjohann@gmx.net (Kai Großjohann)]

Simon Josefsson <jas@extundo.com> writes:

> kai.grossjohann@gmx.net (Kai Großjohann) writes:
>
>> How does nnimap do it?  (I mean where is the entry point into the
>> code where I need to start reading?)
>
> (Warning: This code is so ugly it may make you go blind.)
>
> gnus-fixup-nnimap-unread-after-getting-new-news is invoked via
> gnus-setup-news-hook, and looks like:

(Why is it called "after-getting-new-news" but invoked from
"setup-news-hook" instead of "after-getting-new-news-hook"?)

> (defun gnus-fixup-nnimap-unread-after-getting-new-news ()
>   (let (server group info)
>     (mapatoms
>      (lambda (sym)
>        (when (and (setq group (symbol-name sym))
> 		  (gnus-group-entry group)
> 		  (setq info (symbol-value sym)))
> 	 (gnus-sethash group (cons (nth 2 info) (cdr (gnus-group-entry group)))
> 		       gnus-newsrc-hashtb)))
>      (if (boundp 'nnimap-mailbox-info)
> 	 (symbol-value 'nnimap-mailbox-info)
>        (make-vector 1 0)))))
>
> I.e., it iterates through all nnimap groups and forces the active info
> to be what the variable nnimap-mailbox-info says, which is updated by
> nnimap.

Well...  How about making a new backend function
nnchoke-request-active-info, the corresponding
gnus-request-active-info front-end function, and then the
getting-new-news code looks whether the backends support that
function, and if so, does the above?

That would still be rather ugly, but it would be generalized to other
backends.

What do you think?
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)