From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Another gnu-demon Problem
Date: 16 Apr 1997 00:03:09 +0200 [thread overview]
Message-ID: <m2bu7g2bc2.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Brad Howes's message of 15 Apr 1997 11:10:09 -0700
Brad Howes <bhowes@cssun3.corp.mot.com> writes:
> I've got a "stuck" handler. Its entry in gnus-demon-handler-state never
> gets its time entry reset from zero, so it gets called every minute.
> Watching gnus-demon with edebug, when `(funcall (car handler))' gets
> executed, something is going on so that the following `(setcar...)'
> stuff never does!
Weird. Perhaps something is bugging out, but is being caught and
ignored? That could explain why the execution stops.
I don't really know whether your fix (reversing the statements) is a
good idea or not. Perhaps just slapping an `ignore-errors' around the
calls would be better...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1997-04-15 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-15 18:10 Brad Howes
1997-04-15 22:03 ` Lars Magne Ingebrigtsen [this message]
1997-04-15 23:53 ` Brad Howes
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=m2bu7g2bc2.fsf@proletcult.slip.ifi.uio.no \
--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).