From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: overview -> .db files?
Date: Wed, 06 Nov 2002 12:44:45 -0500 [thread overview]
Message-ID: <m3el9yiod8.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <84fzulnq3s.fsf@crybaby.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 01 Nov 2002 18:42:47 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) wrote:
> Wes Hardaker <wes@hardakers.net> writes:
>> Actually, just making the overview files be .el files would
>> probably be a big win.
nnmaildir does essentially that, with one file per article.
$ cat mail/ding/.nnmaildir/nov/1036172673.12726.multivac.cwru.edu ; echo
[1 1118 "<84fzulnq3s.fsf@crybaby.uni-duisburg.de>" ["Re: overview -> .db files?kai.grossjohann@uni-duisburg.de (Kai =?iso-8859-1?q?Gro=DFjohann?=) Fri, 01 Nov 2002 18:42:47 +0100" "<sdu1j2pp60.fsf@wanderer.hardakers.net> <844rb2o4ef.fsf@crybaby.uni-duisburg.de> <sdela6iamq.fsf@wanderer.hardakers.net> 4841 68" "" (15810 48513) nil]]
> I don't know, however, if Gnus sometimes looks at parts of the
> overview file only.
Sure; nnchoke-retrieve-headers is called with just the range of
articles that Gnus wants to show in the *Summary* buffer.
>> I've often thought that on exiting a summary buffer, you have all the
>> display information since you've already created it, so couldn't we
>> save the current buffer to a file, reload it and reapply all the
>> regions and insert new contents? That *may* be faster than rebuilding
>> it from scratch every time.
I think lots of things could invalidate the stored version, though.
Changes in scoring, gnus-summary-line-format, article marks...
paul
next prev parent reply other threads:[~2002-11-06 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 16:07 Wes Hardaker
2002-10-31 18:21 ` Kai Großjohann
2002-10-31 21:03 ` Wes Hardaker
2002-11-01 17:42 ` Kai Großjohann
2002-11-06 17:44 ` Paul Jarc [this message]
2002-11-07 7:37 ` Kai Großjohann
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=m3el9yiod8.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).