Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Garjola Dindi <garjola@garjola.net>
To: info-gnus-english@gnu.org
Subject: Re: RSS with Gnus (elfeed backend?)
Date: Sun, 04 Apr 2021 11:59:28 +0200	[thread overview]
Message-ID: <87blauv08v.fsf@pc-117-162.ovh.com> (raw)
In-Reply-To: <8735w6zzef.fsf@ericabrahamsen.net>

On Sun 04-Apr-2021 at 02:06:32 +02, Eric Abrahamsen
<eric@ericabrahamsen.net> wrote: 
> 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:
>> 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 :)

Hi Eric,

I have (tried to) read this part of the manual. Not easy, particularly
the fact that the 2 sections on required and optional functions do not
mention de OO interface which appears later.

Right now, I am studying these backends:

nndiscourse - https://github.com/dickmao/nndiscourse.git
nnhackernews - https://github.com/dickmao/nnhackernews.git
gnus-twit - https://github.com/larsmagne/gnus-twit
nntwitter - https://github.com/dickmao/nntwitter.git

And I go back and forth between the manual and the source code of those.

I have also succeeded in generating buffers with contents from elfeed
functions, so I guess its just now a matter of time and struggle.

It is not yet clear to me if there would be an interest in deriving from
nnrss and just reimplementing the appropriate functions.

I have started a repository
(https://gitlab.com/garjola-emacs/nnelfeed/-/tree/master). There is
nothing useful there yet. Just some ideas, but I hope I will be able to
have some progress in the next months.

If anybody can give some pointers to other ressources I could have a
look at, I would be very grateful.

Thanks.

-- 


_______________________________________________
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  9:59 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
2021-04-04  9:59           ` Garjola Dindi [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=87blauv08v.fsf@pc-117-162.ovh.com \
    --to=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).