From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: patch for dynamic updates of the summary buffer while building
Date: Wed, 01 Jan 2003 20:31:08 +0100 [thread overview]
Message-ID: <m3isx81xc3.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <sdhelcf1kx.fsf@wanderer.hardakers.net>
Wes Hardaker <wes@hardakers.net> writes:
> Ok, I got tired of watching the "Building summary buffer" message. It
> turns out (at least if you use threads), it's not to hard to see
> something different. This patch is not exactly perfectly thought out
> and I'm not sure that it'll do strange things on some very customized
> displays (but it works fine on my very customized display).
>
> Now, the summary buffer is built dynamically and I can watch it
> build.
Thanks for the patch; I've applied it to Oort Gnus v0.08 (i. e., CVS).
(I've defaulted `gnus-summary-display-while-building' to nil, though.)
Could you write some documentation for gnus.texi for this?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-01-01 19:31 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
2003-01-01 19:31 ` Lars Magne Ingebrigtsen [this message]
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=m3isx81xc3.fsf@quimbies.gnus.org \
--to=larsi@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).