From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ding@ifi.uio.no
Subject: Re: Long time to exit summary buffer, possible speed enhancement?
Date: Fri, 4 Oct 1996 11:54:33 +0200 (MET DST) [thread overview]
Message-ID: <199610040954.LAA05158@bombur2.uio.no> (raw)
In-Reply-To: <w8sn2y773p0.fsf@hrym.ifi.uio.no>
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
>
>> Why, no. Articles get increasing numbers as they arrive. They will not
>> not interleave. Hmm - except if the article number wraps around. That
>> can happen, right? So *big* holes in ranges must not be collapsed since
>> new articles may be arriving at the beginning of the hole. Instead,
>> nonexisting article numbers should be removed from the beginning of a
>> range following a big hole, to make room for new articles.
>
> Actually, I'm not sure what we're discussing here. I though
> originally it was about article marks, and those lists (or rather,
> ranges) have to be kept precise. If this number of ticked articles is
> wrong, you'll get faulty information displayed.
Huh. Next time, maybe I should read the entire thread before I jump in.
The message I responded to did not seem to say so, but who knows...
Regards,
Hallvard
next prev parent reply other threads:[~1996-10-04 9:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-27 20:28 Shane Holder
1996-09-28 20:08 ` Lars Magne Ingebrigtsen
1996-09-29 9:50 ` Ken Raeburn
1996-09-30 15:21 ` Shane Holder
1996-09-30 15:51 ` Ken Raeburn
1996-09-29 13:09 ` Hallvard B Furuseth
1996-09-29 21:36 ` Ken Raeburn
1996-09-30 6:37 ` Steinar Bang
1996-09-30 15:57 ` Ken Raeburn
1996-09-30 6:34 ` Steinar Bang
1996-10-01 3:39 ` Lars Magne Ingebrigtsen
1996-10-01 14:59 ` Colin Rafferty
1996-10-04 10:00 ` Hallvard B Furuseth
1996-10-04 9:54 ` Hallvard B Furuseth [this message]
1996-10-01 7:07 ` Kai Grossjohann
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=199610040954.LAA05158@bombur2.uio.no \
--to=h.b.furuseth@usit.uio.no \
--cc=ding@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).