From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8186 Path: main.gmane.org!not-for-mail From: Hallvard B Furuseth Newsgroups: gmane.emacs.gnus.general Subject: Re: Long time to exit summary buffer, possible speed enhancement? Date: Fri, 4 Oct 1996 11:54:33 +0200 (MET DST) Message-ID: <199610040954.LAA05158@bombur2.uio.no> References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035148388 10609 80.91.224.250 (20 Oct 2002 21:13:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:13:08 +0000 (UTC) Cc: ding@ifi.uio.no Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.6/8.6.9) with SMTP id DAA01158 for ; Fri, 4 Oct 1996 03:27:55 -0700 Original-Received: from goggins.uio.no (6089@goggins.uio.no [129.240.201.2]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id ; Fri, 4 Oct 1996 11:54:45 +0200 Original-Received: from ulrik.uio.no by goggins.uio.no with local-SMTP (PP) id <18750-0@goggins.uio.no>; Fri, 4 Oct 1996 11:54:35 +0200 Original-Received: by bombur2.uio.no ; Fri, 4 Oct 1996 11:54:33 +0200 (MET DST) Original-To: Lars Magne Ingebrigtsen In-reply-to: Xref: main.gmane.org gmane.emacs.gnus.general:8186 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8186 Lars Magne Ingebrigtsen writes: >Hallvard B Furuseth 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