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
Cc: "Jose A. Ortega Ruiz" <jao@gnu.org>
Subject: Re: RSS with Gnus (elfeed backend?)
Date: Fri, 02 Apr 2021 08:43:07 +0200	[thread overview]
Message-ID: <87tuopnq4k.fsf@pc-117-162.ovh.com> (raw)
In-Reply-To: <87ft09n77r.fsf@gnus.jao.io>

On Thu 01-Apr-2021 at 21:19:20 +02, "Jose A. Ortega Ruiz" <jao@gnu.org>
wrote: 
> Hi,
>
> Not exactly what you're suggesting, but i've used rss2email for years
> now, and it works pretty well (the package in debian keeps getting
> updates, and it's working with the latest 3.9 python).  Instead of
> putting the emails in a maildir directly, it sends an email to a (local)
> address of your choice.
>
> HTH,
> jao

Hi José,

Thanks for the hint! It seems an interesting replacement for feeds2imap.
I guess that all feeds go to the same e-mail address and that you use
splitting to create different groups? Would you be willing to share your
configuration?

I am still interested in the pure elisp route. I have had a look at the
elfeed source code and is seems rather modular and using its API seems
feasible.

On the other hand, I have had a look at the code of some Gnus backends
(hacker news, reddit) and I don't understand what is needed to build
one. 

Is there any example of Gnus backend which can be suggested as an
introductory tutorial? I am going to study the relevant section of the
Gnus info manual, but any advice would be welcome.

Thanks everybody.

G.

-- 


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

  reply	other threads:[~2021-04-02  6:44 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 [this message]
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

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=87tuopnq4k.fsf@pc-117-162.ovh.com \
    --to=garjola@garjola.net \
    --cc=info-gnus-english@gnu.org \
    --cc=jao@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).