Re: Concerning marks and the back end.

[Lloyd Zusman <ljz@asfast.com>]

Simon Josefsson <jas@extundo.com> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>>
>> [ ... ]
>>
>> Is there any way to make the "display" parameter only apply when there
>> are no unread messages at all in the group?
>
> You can set the display parameter to an array of predicates, e.g.:
>
> [or unread (and no-unreads my-article-old-p)]
>
>      (defun my-article-old-p ()
>        "Say whether an article is old."
>        (< (time-to-days (date-to-time (mail-header-date gnus-headers)))
>           (- (time-to-days (current-time)) gnus-agent-expire-days)))
>
> implementing the no-unreads function is left as an exercise. :-)
>
> But this might not work either, as I think display predicates was
> implemented as limiting, so you will fetch all article headers anyway.

Hmmm ... well, I could always cheat and use `defadvice' to wrap the
function which enters the group; and I would use `let' to cover the
variable that contains the `display' value that we discussed earlier.
The `no-unreads' value has got to be available somewhere in the Group
buffer, because it gets displayed to the left of the group name in that
buffer.  So if that no-unreads value is non-zero, I would set the
covered `display' value to nil, otherwise, to 100 or something.

Sounds easy, anyway. :)


> But I still wonder why entering the group is slow for you.  I have
> 15,000 messages in my ding mailing list mailbox, which is stored on a
> IMAP server, and entering it and viewing the unread and ticked
> articles takes no time.  When I get several hundred thousand articles
> it becomes a little slow though (long coffe break).

Well, I still will do the profiling that you suggested earlier.

I wonder if in my case things would be slower than for you because ...

1. I'm having this problem in nnml and nnspool groups, and not nnimap,
   which I'm not using these days.

2. I have a custom summary line format string that makes use of a
   couple of custom format functions that I wrote ... this will
   probably turn out to be the culprit.

Well, all will become much clearer after I run the profiler.

-- 
 Lloyd Zusman
 ljz@asfast.com