Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Marsden <emarsden@mail.dotcom.fr>
Cc: ding@gnus.org
Subject: Re: Announce: nnwarchive
Date: 09 Nov 1999 19:39:15 +0100	[thread overview]
Message-ID: <wzi3dufjyr0.fsf@mail.dotcom.fr> (raw)
In-Reply-To: Shenghuo ZHU's message of "09 Nov 1999 13:25:15 -0500"

>>>>> "ZSH" == Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>>>>> "ecm" == Eric Marsden <emarsden@mail.dotcom.fr> writes:

  ecm> So I am wondering if there is scope for a generic "wash.el"
  ecm> which would take as an argument an URL (which is dynamically
  ecm> generated in certain cases), a parser function which returns
  ecm> matches, operating on the raw HTML, and provides automatic or
  ecm> semi-automatic update services which connect to some trusted
  ecm> web site where washing-authors can put updates.

  ZSH> A generic "wash.el" is not easy. Different pages need different
  ZSH> wash. Some pages need rebuild headers, some others need dissect
  ZSH> a page into several articles. A generic "wash.el" would have to
  ZSH> use callback functions or so. However, a "wash-util.el" may be
  ZSH> possible.

I was thinking of an interface something like

  (wash url-generator washer)

where URL-GENERATOR is a function which takes `&rest args', and WASHER
is a function which operates on the current buffer and returns a list
of items (of arbitrary type, to be interpreted by the caller).

But the area where there's the most scope for reuse IMO is in the
semi-automatic updates. The current state of nnweb.el shows that there
is a need for auto-updates, and I think it would be easier for users
to trust a single module (which connects to a trusted server) to
download new code to be run in their emacs.
 
-- 
Eric Marsden
It's elephants all the way down


  reply	other threads:[~1999-11-09 18:39 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
1999-11-09 18:39     ` Eric Marsden [this message]
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=wzi3dufjyr0.fsf@mail.dotcom.fr \
    --to=emarsden@mail.dotcom.fr \
    --cc=ding@gnus.org \
    /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).