Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Concerning marks and the back end.
Date: Fri, 03 Jan 2003 05:11:08 +0100	[thread overview]
Message-ID: <iluwulmootf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86el7vc4xw.fsf@asfast.com> (Lloyd Zusman's message of "Thu, 02 Jan 2003 22:01:15 -0500")

Lloyd Zusman <ljz@asfast.com> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> [ ... ]
>>>
>>> Maybe you can use this approach to accomplish something similar: set
>>> the group parameter "display" (G c) to a value that makes group
>>> entering fast (e.g. 500).  If you ever want to see older articles,
>>> enter the group with C-u SPC.  If you want to keep around a specific
>>> article even after falls outside of the 500 limit, press ! on it.
>>
>> Aha!  Yes, that would work splendidly to give me pretty much exactly
>> what I want.
>>
>> Great idea ... and now, as far as I'm concerned, Problem Solved.
>>
>> Thanks a lot.
>
> ... but then again ...
>
> I just noticed something less-than-ideal about this.  For example,
> suppose a group has 10 unread messages and 6 zillion already read
> messages.  I set the "display" paramter to 100 as discussed above, and I
> then enter the group.  I now see the 10 new unread messages interspersed
> among 90 already-read messages.
>
> 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.

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).




  reply	other threads:[~2003-01-03  4:11 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 22:23 Lloyd Zusman
2003-01-02 16:57 ` Kai Großjohann
2003-01-02 18:23   ` Lloyd Zusman
2003-01-02 18:46     ` Lars Magne Ingebrigtsen
2003-01-03  2:23       ` Lloyd Zusman
2003-01-03  2:45         ` Simon Josefsson
2003-01-03  2:56           ` Lloyd Zusman
2003-01-03  3:01             ` Lloyd Zusman
2003-01-03  4:11               ` Simon Josefsson [this message]
2003-01-03  4:59                 ` Lloyd Zusman
2003-01-03 14:57                   ` Simon Josefsson
2003-01-04 18:23                   ` Lloyd Zusman
2003-01-13 18:47                     ` A solution that's better than my ugly hack? Lloyd Zusman
2003-01-13 18:53                       ` Lars Magne Ingebrigtsen
2003-01-13 19:00                         ` Lloyd Zusman
2003-01-13 19:18                           ` Lars Magne Ingebrigtsen
2003-01-13 19:26                             ` Lloyd Zusman
2003-01-13 19:30                               ` Lars Magne Ingebrigtsen
2003-01-13 19:33                                 ` Lloyd Zusman
2003-01-13 21:04                                 ` Lloyd Zusman
2003-01-13 19:32                               ` Lloyd Zusman
2003-01-03 17:54         ` Concerning marks and the back end Kai Großjohann
2003-01-03 18:20           ` Lloyd Zusman
2003-01-03 17:53     ` Kai Großjohann
2003-01-03 18:15       ` Lloyd Zusman
2003-01-03 19:18         ` Kai Großjohann
2003-01-03 19:34           ` Lloyd Zusman
2003-01-03 19:43             ` Lloyd Zusman
2003-01-03 21:03               ` Kai Großjohann
2003-01-03 21:24                 ` Lloyd Zusman
2003-01-04 14:52                   ` Kai Großjohann
2003-01-04 16:19                     ` Lloyd Zusman
2003-01-03 20:17             ` Lars Magne Ingebrigtsen
2003-01-03 20:41               ` Lloyd Zusman
2003-01-03 20:45                 ` Lars Magne Ingebrigtsen
2003-01-03 20:52                   ` Lloyd Zusman
2003-01-03 21:05                     ` Kai Großjohann
2003-01-03 21:05                 ` Kai Großjohann
2003-01-04  4:50                   ` Lloyd Zusman
2003-01-03 20:53             ` Paul Jarc
2003-01-03 20:58               ` Lloyd Zusman
2003-01-03 21:02             ` Kai Großjohann
2003-01-02 19:14 ` Simon Josefsson
2003-01-03  2:25   ` Lloyd Zusman

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=iluwulmootf.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).