From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Blue (or was it yellow?) GNUS suggestions
Date: 31 May 1996 09:28:28 +0200 [thread overview]
Message-ID: <x691e9z4gz.fsf@eyesore.no> (raw)
In-Reply-To: "Sudish Joseph"'s message of 28 May 1996 18:59:01 -0400
"Sudish Joseph" <sudish@VNET.IBM.COM> writes:
> IMO, it'd be a big win if GNUS went ahead and prepared the summary
> for the headers it already has, thus distributing the cost of
> summary generation over the time wasted waiting for all headers.
Yeah, that would be ultra-kool. Hm. One could do this sort of thing
without having an external threader type thing as well. But one would
have to write the thing in C. Updating/removing/inserting things in
this manner in Elisp would just be far too slow.
But it would be seriously cool.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-05-31 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-25 21:31 Sudish Joseph
1996-05-27 1:49 ` Lars Magne Ingebrigtsen
1996-05-28 0:45 ` Sudish Joseph
1996-05-28 19:52 ` Lars Magne Ingebrigtsen
1996-05-28 22:59 ` Sudish Joseph
1996-05-29 9:30 ` Per Abrahamsen
1996-05-31 7:28 ` 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=x691e9z4gz.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).