From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: gnus-demon question
Date: Tue, 04 Jan 2011 08:54:31 +0100 [thread overview]
Message-ID: <874o9pdryg.fsf@member.fsf.org> (raw)
In-Reply-To: <m37helfsdo.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 04 Jan 2011 01:02:27 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Hi!
>> (gnus-demon-add-handler 'gnus-group-get-new-news 15 t)
>
> I've never used that, and I'm not sure whether that's supposed to work
> or not. Anybody?
I use this (first param is TIME, second is IDLE)
(gnus-demon-add-handler 'gnus-demon-scan-news 15 5)
The docs say
,----[ (info "(gnus)Daemons") ]
| If IDLE is a number and TIME is a number, the function will be
| called every TIME minutes only when Emacs has been idle for IDLE
| minutes.
`----
so I'd expect it to run every 15 minutes but only if emacs has been idle
for 5 minutes.
Nevertheless, that doesn't match my observations. It seems, that the
docs are correct for the first run, but any subsequent run doesn't check
if emacs has been idle. Often, I'm writing in emacs, do a 15 seconds
thinking pause, and then I can see Gnus checking for new mail/news.
Well, because that's so fast nowadays, it's not a big issue for me. But
the docs don't seem to be correct...
Bye,
Tassilo
--
Sent from my Emacs
prev parent reply other threads:[~2011-01-04 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 6:47 Noorul Islam K M
2010-12-22 7:49 ` Tassilo Horn
2010-12-22 8:49 ` Noorul Islam K M
2011-01-03 11:58 ` Noorul Islam K M
2011-01-04 0:02 ` Lars Magne Ingebrigtsen
2011-01-04 5:58 ` Noorul Islam K M
2011-01-04 11:34 ` Adam Sjøgren
2011-01-04 12:06 ` Noorul Islam K M
2011-01-04 12:56 ` Adam Sjøgren
2011-01-04 13:13 ` Robert Pluim
2011-01-04 14:22 ` Adam Sjøgren
2011-01-04 14:47 ` Adam Sjøgren
2011-01-04 16:56 ` Tassilo Horn
2011-01-04 18:02 ` Adam Sjøgren
2011-01-06 17:12 ` Philipp Haselwarter
2011-01-09 14:28 ` Noorul Islam
2011-01-04 7:54 ` Tassilo Horn [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=874o9pdryg.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--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).