From: Nasser Alkmim <nasser.alkmim@gmail.com>
To: ding@gnus.org
Subject: Strategies for idle fetching of messages
Date: Thu, 15 Feb 2024 07:54:34 +0100 [thread overview]
Message-ID: <87bk8iqkt1.fsf@gmail.com> (raw)
Hi,
I'm attempting to improve my Gnus workflow by avoiding the waiting time
when checking and fetching new messages.
I read the manual and tried a couple of strategies, however it is not
working as intended.
I tried this workflow:
1. Open gnus and check groups only up to level 2 (this should be quick).
2. When idle, get messages from all other groups up to level 5.
The number 2 is not working properly.
My configuration for that is:
(defun gnus-demon-scan-news-5 ()
(interactive)
(let ((win (current-window-configuration)))
(unwind-protect
(save-window-excursion
(when (gnus-alive-p)
(with-current-buffer gnus-group-buffer
(gnus-group-get-new-news 5))))
(set-window-configuration win))))
(gnus-demon-add-handler 'gnus-demon-scan-news-5 1 t)
Ideally, I would want the messages to be readily available the next time
I open gnus again. Is that possible?
What are your strategies?
--
Nasser Alkmim
+43 677 6408 9171
reply other threads:[~2024-02-15 17:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87bk8iqkt1.fsf@gmail.com \
--to=nasser.alkmim@gmail.com \
--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).