From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Announce: nnwarchive
Date: 09 Nov 1999 13:25:15 -0500 [thread overview]
Message-ID: <5baeoncyk4.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Eric Marsden's message of "09 Nov 1999 18:52:20 +0100"
>>>>> "ecm" == Eric Marsden <emarsden@mail.dotcom.fr> writes:
[...]
ecm> So I am wondering if there is scope for a generic "wash.el" which
ecm> would take as an argument an URL (which is dynamically generated
ecm> in certain cases), a parser function which returns matches,
ecm> operating on the raw HTML, and provides automatic or
ecm> semi-automatic update services which connect to some trusted web
ecm> site where washing-authors can put updates.
A generic "wash.el" is not easy. Different pages need different wash.
Some pages need rebuild headers, some others need dissect a page into
several articles. A generic "wash.el" would have to use callback
functions or so. However, a "wash-util.el" may be possible.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-11-09 18:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 17:02 Shenghuo ZHU
1999-11-09 17:52 ` Eric Marsden
1999-11-09 18:25 ` Shenghuo ZHU [this message]
1999-11-09 18:39 ` Eric Marsden
1999-11-09 18:54 ` Kai Großjohann
1999-11-09 19:11 ` Eric Marsden
1999-11-10 8:44 ` Kai Großjohann
1999-11-10 9:09 ` Eric Marsden
1999-11-10 15:28 ` Lars Magne Ingebrigtsen
1999-11-10 21:59 ` Kai Großjohann
1999-11-11 15:34 ` Lars Magne Ingebrigtsen
1999-11-11 18:14 ` Kai Großjohann
1999-11-11 23:11 ` Karl EICHWALDER
[not found] ` <vafiu38zyj4.fsf@ <shln84r5cy.fsf@tux.gnu.franken.de>
1999-11-12 9:12 ` Kai Großjohann
1999-11-12 10:14 ` Steinar Bang
1999-11-12 12:19 ` Kai Großjohann
1999-11-10 15:32 ` Lars Magne Ingebrigtsen
1999-11-10 16:12 ` Eric Marsden
1999-11-11 15:35 ` Lars Magne Ingebrigtsen
1999-11-09 19:12 ` Shenghuo ZHU
1999-11-10 15:25 ` Lars Magne Ingebrigtsen
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=5baeoncyk4.fsf@giga.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).