Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Read Heise newsticker: hackers wanted
Date: Tue, 12 Feb 2002 10:01:30 +0100	[thread overview]
Message-ID: <vafit93ysyd.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <gd.y1y3d07vrmb.fsf@fly.verified.de> (Raymond Scholz's message of "Mon, 11 Feb 2002 18:46:20 +0100")

Raymond Scholz <ray-2002@zonix.de> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Do you think it makes sense to incorporate this into Gnus in some
>> way?  (It needs to be polished up before that.)
>
> Hm, what about the idea of separating moving targets like those rss
> functions, nnslashdot, nnwarchive etc. from the main Gnus
> distribution?  It'll be helpful for users that don't want to upgrade
> to Gnus development versions just for the sake of reading those news
> services.

That is a good idea.  But it seems nobody has stepped forward to do
the work.

> But I've no good idea how to implement this.  Should there be a
> subscription service (mailing list or some "Gnus news channel" within
> Gnus itself)?  What kind of information should be transferred (plain
> Elisp files or some meta format to be defined)?

It might be better to factor out the parsing code and to distribute
it.  Maybe the parsing is done via regexes, then regexes could be
factored out.  Or maybe the parsing is done via XPath, then XPath
queries could be factored out.  Or a Lisp function, for full
generality.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)



      reply	other threads:[~2002-02-12  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 20:16 Kai Großjohann
2002-02-11  9:14 ` Kai Großjohann
2002-02-11  9:34   ` Kai Großjohann
2002-02-11 17:46     ` Raymond Scholz
2002-02-12  9:01       ` Kai Großjohann [this message]

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=vafit93ysyd.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).