From: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Idle Time to Poll Serve
Date: Thu, 20 Feb 2020 19:25:25 +0100 [thread overview]
Message-ID: <87d0a93ylm.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <48946.8263041758$1582218959@news.gmane.org>
As your approach is giving you problems, maybe it would make sense to
look into Gnus' demons?
· http://gnus.org/manual/gnus_119.html#Daemons
I use this:
; Demon to fetch email every 5 minutes when Emacs has been idle for 5 minutes:
(gnus-demon-add-handler 'gnus-demon-scan-news 5 5)
; Demon to send queued email every other minute:
(gnus-demon-add-handler 'gnus-delay-send-queue 1 nil)
(gnus-demon-init)
To my surprise, the manual doesn't mention gnus-demon-scan-news, which I
would think was the most obvious one to write about...
Hm, maybe it is obsolete? I guess this is the current way:
,----[ C-h f gnus-demon-add-rescan RET ]
| gnus-demon-add-rescan is an autoloaded compiled Lisp function in
| ‘gnus-demon.el’.
|
| (gnus-demon-add-rescan)
|
| Add daemonic scanning of new articles from all backends.
`----
?
Best regards,
Adam
--
"Lidt som at skylle en pose lakridskonfekt ned med Adam Sjøgren
en flaske Kahlua, men det kan jo også have sin asjo@koldfront.dk
egen diskrete charme"
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-02-20 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:05 Richmond
2020-02-20 16:41 ` Eric Abrahamsen
2020-02-20 16:52 ` Richmond
2020-02-20 17:15 ` Richmond
2020-02-20 17:44 ` Eric Abrahamsen
2020-02-20 18:25 ` Adam Sjøgren via info-gnus-english [this message]
2020-02-20 22:02 ` Richmond
2020-02-21 7:35 ` Adam Sjøgren via info-gnus-english
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=87d0a93ylm.fsf@tullinup.koldfront.dk \
--to=info-gnus-english@gnu.org \
--cc=asjo@koldfront.dk \
/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).