Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Cc: ding@gnus.org
Subject: Re: Gnus is very slow in displaying headers.
Date: Wed, 25 Aug 2004 09:14:21 +0200	[thread overview]
Message-ID: <86zn4j665u.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: <8yc4d5gh.fsf@random.internal> (Derrell Lipman's message of "Tue, 24 Aug 2004 09:35:26 -0400")

Derrell.Lipman@UnwiredUniverse.com writes:

> Kai Grossjohann <kai@emptydomain.de> writes:
>
>> Some people like to keep lots of articles marked as unread, especially
>> for mail, so that they do not lose track of the context.  But I think
>> that it works well to (setq gnus-fetch-old-headers t): this leads to
>> Gnus showing the complete thread, if there is an unread article in
>> that thread.  This way, I get the complete context of new discussions,
>> without having to keep all old articles of this discussion unread.
>
> I used to do that.  Based on a previous thread in the ding list about slow
> presentation of a group, I now have the following comment and setting in my
> .gnus file:
>
>     (setq
>      ;; Show headers of previous messages in a thread
>      ;; Don't do this; it greatly slows down presentation of the group
>      gnus-fetch-old-headers			nil
>     )
>
> My recollection was that the difference in speed, disabling this, was
> remarkable.

Well, what do I say about this?

Many people have many articles marked as unread.  It is faster to mark
them as read and (setq gnus-fetch-old-headers t) -- this tends to show
the "interesting" articles that people would otherwise mark as unread.

Obviously, not showing the "interesting" articles is faster still.
But then, people might tend to mark interesting articles as unread,
leading to 12,000 unread articles in a group, which leads to the
slowdown.

Kai




  parent reply	other threads:[~2004-08-25  7:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  3:40 Daniel M.
2004-08-23 12:12 ` Jorge Godoy
2004-08-24  6:02   ` Daniel M.
2004-08-23 20:22     ` Jorge Godoy
2004-08-24  4:49 ` Kevin Greiner
2004-08-24 17:30   ` Daniel M.
2004-08-24  9:31     ` Kai Grossjohann
2004-08-24 19:44       ` Daniel M.
2004-08-24 12:05         ` Kai Grossjohann
2004-08-24 13:35           ` Derrell.Lipman
2004-08-25  6:08             ` Daniel M.
2004-08-25  7:14             ` Kai Grossjohann [this message]
2004-08-25  6:26           ` Daniel M.
2004-08-24 20:54             ` Andrew A. Raines
2004-08-25  8:57             ` Kai Grossjohann
2004-08-24 20:07 ` Jesper Harder
2004-08-25  6:34   ` Daniel M.
2004-08-26 14:50 ` ignotus
2004-08-27 23:24   ` Daniel M.

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=86zn4j665u.fsf@ketchup.de.uu.net \
    --to=kai@emptydomain.de \
    --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).