From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Seeming gnus-demon-* inconsistency.
Date: 12 Aug 2000 21:32:05 +0200 [thread overview]
Message-ID: <m3r97uff7u.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ltd7muth6y.fsf@asfast.com>
Lloyd Zusman <ljz@asfast.com> writes:
> Scenario A:
>
> (setq gnus-demon-timestep 60)
> (gnus-demon-add-handler 'my-demon-function 1 t)
>
> Scenario B:
>
> (setq gnus-demon-timestep 1)
> (gnus-demon-add-handler 'my-demon-function 60 t)
>
> It seems to me that these two scenarios should produce identical
> results:
Yup.
> that `my-demon-function' would get invoked after each block of 60
> seconds of idle time. However, that scenario only seems to take
> place in Scenario B. In Scenario A, often several minutes of idle
> time pass before `my-demon-function' is invoked.
That's odd. Scenario A is the default, after all, and I haven't seen
any reports saying that it doesn't work... (Of course, me not having
seen such a report doesn't mean that it hasn't been submitted. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-08-12 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-10 18:04 Lloyd Zusman
2000-08-12 19:32 ` Lars Magne Ingebrigtsen [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=m3r97uff7u.fsf@quimbies.gnus.org \
--to=larsi@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).