Gnus development mailing list
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: Update RSS feeds less frequently
Date: Sat, 17 Dec 2022 09:45:14 -1000	[thread overview]
Message-ID: <87k02p4xx1.suxaily@xguglv.tcqwbgdiu.com> (raw)
In-Reply-To: <87pmci6ld1.fsf@johnhaman.org> (John Haman's message of "Sat, 17 Dec 2022 11:33:30 -0500")


>> Use levels ("S l" in the group buffer to give individual groups a
>> level); info manual section (gnus) Group Levels.  Give the low traffic
>> groups a higher level than the default retrieved and then manually (C-u
>> 5 g, say) retrieve higher level groups every so often.

I've used this method for some time and it's quite effective,
with one twist.  All groups of all levels are retrieved on
Emacs startup.  After that I do manual refresh of any group
(RSS feeds in particular) that may interest me.  This prevents
slowdown of high-priority mail fetching, such as my inbox.

> I have never heard about rss2email. I might give it a shot, but I'm not
> a fan of mixing email and rss together, even if I separate feeds into
> different folders.

For Gnus, it seems to me there's hardly any difference.  Your
feeds end up in Gnus groups, no matter how they happened to
have gotten there. Alternatively, though, if you want complete
separation but still staying within Emacs, you can use
something like elfeed.

-- 
Bob Newell
Honolulu, Hawai`i

- Via GNU/Linux/Emacs/Gnus/BBDB


      parent reply	other threads:[~2022-12-17 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  4:08 John Haman
2022-12-17  7:43 ` Bodertz
2022-12-17 12:50 ` Eric S Fraga
2022-12-17 16:33   ` John Haman
2022-12-17 16:59     ` Adam Sjøgren
2022-12-17 19:31       ` John Haman
2022-12-19 20:44         ` Haider Rizvi
2022-12-19 21:04         ` Bob Newell
2022-12-20  1:23           ` John Haman
2022-12-21 22:05             ` Bob Newell
2022-12-17 19:45     ` Bob Newell [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=87k02p4xx1.suxaily@xguglv.tcqwbgdiu.com \
    --to=bobnewell@bobnewell.net \
    --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).