From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8358
Path: main.gmane.org!not-for-mail
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: Web-based mailreading enhancement
Date: 12 Oct 1996 19:45:42 +0100
Message-ID: <x6k9swf2cp.fsf@eyesore.no>
References: <byvicjkwb1.fsf@math.ethz.ch> 	<x6pw2q30mi.fsf@eyesore.no> 	<qk27moyov7t.fsf@iptsun2.unil.ch> 	<whd8ypg8ua.fsf@norne.metis.no> 	<whwwwxejf9.fsf@norne.metis.no> 	<w8s20f58wx1.fsf@ylfing.ifi.uio.no> <199610111558.IAA22317@newman.aventail.com>
NNTP-Posting-Host: coloc-standby.netfonds.no
X-Trace: main.gmane.org 1035148531 11688 80.91.224.250 (20 Oct 2002 21:15:31 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sun, 20 Oct 2002 21:15:31 +0000 (UTC)
Return-Path: <ding-request@ifi.uio.no>
Original-Received: (qmail 6705 invoked from smtpd); 12 Oct 1996 18:16:25 -0000
Original-Received: from ifi.uio.no (0@129.240.64.2)
  by deanna.miranova.com with SMTP; 12 Oct 1996 18:16:25 -0000
Original-Received: from ylfing.ifi.uio.no (4867@ylfing.ifi.uio.no [129.240.94.25]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) 
	id <TAA18669@ifi.uio.no> for <ding@ifi.uio.no> ; Sat, 12 Oct 1996 19:58:02 +0200
Original-Received: (from larsi@localhost) by ylfing.ifi.uio.no ; Sat, 12 Oct 1996 19:57:59 +0200
Original-To: ding@ifi.uio.no
In-Reply-To: William Perry's message of Fri, 11 Oct 1996 08:58:11 -0700
Original-Lines: 21
X-Mailer: Red Gnus v0.51/Emacs 19.29
X-Face: &w!^oO<W.WBH]FsTP:P0f9X6M-ygaADlA_)eF$<UwQzj7:C=Gi<a?/_4$LX^@$Qq7-O&XHp
 lDARi8e8iT<(A$LWAZD*xjk^')/wI5nG;1cNB>~dS|}-P0~ge{$c!h\<y
Xref: main.gmane.org gmane.emacs.gnus.general:8358
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8358

William Perry <wmperry@aventail.com> writes:

>   I don't think you can.  You might be able to do something heinous with
> the information in the big 'summary' view that hypermail can use.  It gives
> you the URLs, the subject, and I think the author's 'nice' name (William
> Perry instead of 'wmperry@aventail.com').

That's not overly much, but it would allow generating kinda nice
summary buffers.

>   I don't think you would want to do this with regexp's on the HTML though.
> The 'threading' view is done by using nested lists.  Relatively easy to
> handle from the parser (its even iterative! ;) though.

I should probably junk the regexp'y HTML "parsing" done now and rely
on w3 instead.  That would be much more resist{a,e}nt to changes in output
from the search engines and would be nicer all over.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."