From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6431
Path: main.gmane.org!not-for-mail
From: Per Abrahamsen <abraham@dina.kvl.dk>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: Blue (or was it yellow?) GNUS suggestions
Date: 29 May 1996 11:30:07 +0200
Sender: abraham@dina.kvl.dk
Message-ID: <rjohn7u8rk.fsf@kleene.dina.kvl.dk>
References: <199605252131.RAA00636@atreides> <x6afyuc2be.fsf@eyesore.no>
	<199605280045.UAA00274@atreides> <x6ohn87ez8.fsf@eyesore.no>
	<m24tp0xv4a.fsf@galaxy.atlissc.ibm.com>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1035146887 3569 80.91.224.250 (20 Oct 2002 20:48:07 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sun, 20 Oct 2002 20:48:07 +0000 (UTC)
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.5/8.6.9) with SMTP id DAA00935 for <steve@miranova.com>; Wed, 29 May 1996 03:22:20 -0700
Original-Received: from elc1.dina.kvl.dk (elc1.dina.kvl.dk [130.225.40.228]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) 
	id <LAA17532@ifi.uio.no> for <ding@ifi.uio.no> ; Wed, 29 May 1996 11:30:42 +0200
Original-Received: from kleene.dina.kvl.dk (kleene.dina.kvl.dk [130.225.40.223]) by elc1.dina.kvl.dk (8.6.12/8.6.4) with ESMTP id LAA06778; Wed, 29 May 1996 11:30:08 +0200
Original-Received: (abraham@localhost) by kleene.dina.kvl.dk (8.6.12/8.6.4) id LAA12669; Wed, 29 May 1996 11:30:08 +0200
Original-To: ding@ifi.uio.no
X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM<U{B+4e{k79.Ya{~':DblFPCg$
 @60,BfLv2@SKZ19cMWK0/C'v;tM:|6B'R}U1rp6CL&kN({9<zF/V{:JCg27yC)9oZjeqcQawzKfiNL
 t9}`vjmK["dRQC/qGFQq"%u|Q`:6{"Rz}b(dnl_"3$Jtqimi>|8MBp/
In-Reply-To: "Sudish Joseph"'s message of 28 May 1996 18:59:01 -0400
Original-Lines: 8
X-Mailer: Gnus v5.2.1/Emacs 19.31
Xref: main.gmane.org gmane.emacs.gnus.general:6431
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6431


I don't know about how practical it would be, but the visual effect of
a summary that was being build/threaded/sorted concurrently with the
incoming headers would be stunning.

You'd need an `add-this-header-to-the-summary-buffer' command, and a
process watch that call that function each time a new header becomes
available.