Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Gnus is very slow in displaying headers.
Date: Tue, 24 Aug 2004 14:05:39 +0200	[thread overview]
Message-ID: <868yc43fn0.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: <hf6ni0p9o1b8gvktn42bjjpa6t6kavjqg4@4ax.com>

Daniel M. <xt@nm.ru> writes:

>>Does it help to put (gnus-compile) after the (setq
>>gnus-summary-line-format ...) statement?
>
> Unfortunatley not at all - it still takes the same 1 min. 37 sec.
> to load the group. For 26 sec. the status line reads: "Fetching
> headers for comp.lang.lisp" (the group I ma loading), then
> for the rest of the time: "Generating summary".

I see.  I'm afraid that probably most people do not open groups with
that many articles.  The time used for summary generation depends on
the length of the summary buffer.

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.

So my question to you is: why are there 12,000 unread articles in that
group?  I'm suspecting that you don't intend to read them all...

Kai




  reply	other threads:[~2004-08-24 12:05 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 [this message]
2004-08-24 13:35           ` Derrell.Lipman
2004-08-25  6:08             ` Daniel M.
2004-08-25  7:14             ` Kai Grossjohann
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=868yc43fn0.fsf@ketchup.de.uu.net \
    --to=kai@emptydomain.de \
    /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).