Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Garjola Dindi <garjola@garjola.net>
Cc: info-gnus-english@gnu.org
Subject: Re: RSS with Gnus (elfeed backend?)
Date: Sat, 03 Apr 2021 17:06:32 -0700	[thread overview]
Message-ID: <8735w6zzef.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87im53omef.fsf@pc-117-162.ovh.com> (Garjola Dindi's message of "Sat, 03 Apr 2021 09:30:32 +0200")

Garjola Dindi <garjola@garjola.net> writes:

> On Fri 02-Apr-2021 at 20:21:07 +02, Tim Landscheidt
> <tim@tim-landscheidt.de> wrote: 
>> Garjola Dindi <garjola@garjola.net> wrote:
>>>
>> It's even worse because Emacs already has yet another (rath-
>> er fragile) RSS reader, newsticker, that AFAIR does not
>> share code with either, and nnrss has an asynchronous, yet
>> somewhat manual out-of-Gnus retriever
>> (nnrss-generate-download-script), the keys for moving to the
>> next or the next unread article in newsticker are "reversed"
>> compared to Gnus, elfeed seems to have a separate system for
>> scoring articles, etc., etc., etc.  newsticker as well as
>> nnrss feel like "technology demonstrators", i. e., yeah, you
>> can read RSS feeds in Emacs or Gnus, but nobody really does.
>>
>
> And there is also org-feed.el which generates an org-mode outline from
> RSS or Atom feeds.
>
>> So if someone would implement a (preferably new) nice, clean
>> backend for Gnus that DWIM, I'd be eternally grateful :-).
>
> I have spent some time reading elfeed's source code and it provides a
> nice API. What I don't like about elfeed is that it is «entry-oriented»,
> that is, all articles are dumped in the same inbox and all the selection
> operations are done through tags. I think that a Gnus back-end could use
> elfeed's API to filter the entries and generate the content of Gnus's
> groups (one group per feed, for instance), while all the feed updating,
> downloading, etc. could be delegated to elfeed.
>
> What I have in mind is writing a light Gnus backend (inspired for
> instance from the one for Twitter that Lars Ingebrigtsen wrote [1]) that
> just uses elfeed behind the scenes.
>
> The difficulty is that I do not understand how a Gnus backend works, so
> I will have to study this first. 
>
> If anybody can point to an easy to understand Gnus backend to get me
> started, I would be very grateful.

Check the "Gnus Reference Guide" section of the Gnus manual, in
particular the second section, "Back End Interface". But you won't like
it :)

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2021-04-04  0:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 18:59 Garjola Dindi
2021-04-01 19:19 ` Jose A. Ortega Ruiz
2021-04-02  6:43   ` Garjola Dindi
2021-04-02 20:44     ` Jose A. Ortega Ruiz
2021-04-03  7:34       ` Garjola Dindi
2021-04-02 15:04 ` Jeffrey DeLeo
2021-04-02 15:29   ` Garjola Dindi
2021-04-02 18:21     ` Tim Landscheidt
2021-04-03  7:30       ` Garjola Dindi
2021-04-04  0:06         ` Eric Abrahamsen [this message]
2021-04-04  9:59           ` Garjola Dindi

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=8735w6zzef.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=garjola@garjola.net \
    --cc=info-gnus-english@gnu.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).