From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: patch for dynamic updates of the summary buffer while building
Date: Mon, 13 May 2002 19:05:55 -0700 [thread overview]
Message-ID: <sdvg9rlbzw.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <m38z6nsdre.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 14 May 2002 03:45:57 +0200")
>>>>> On Tue, 14 May 2002 03:45:57 +0200, Jesper Harder <harder@ifa.au.dk> said:
Jesper> It makes summary buffer generation 30-40% slower, though, so
Jesper> I'm sure it should be turned on by default.
Yeah, you need to set the display update to something reasonable. The
default of 5 is probably too small. 20 would probably be better.
I've thought, over the day, that maybe a percentage would be best.
IE, .05 would mean 5% and thus for really large groups wouldn't be
that frequent, but it wouldn't slow it down as much.
--
"The trouble with having an open mind, of course, is that people will
insist on coming along and trying to put things in it." -- Terry Pratchett
next prev parent reply other threads:[~2002-05-14 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:35 Wes Hardaker
2002-05-14 1:45 ` Jesper Harder
2002-05-14 2:05 ` Wes Hardaker [this message]
2003-01-01 19:31 ` Lars Magne Ingebrigtsen
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=sdvg9rlbzw.fsf@wanderer.hardakers.net \
--to=wes@hardakers.net \
--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).