From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Saving some read IMAP messages to a local folder
Date: Fri, 07 Feb 2003 13:23:18 +0100 [thread overview]
Message-ID: <m3y94scma1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <iluof5r6xz1.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> I committed the patch. While at it, I started cleaning up
> gnus-agent-expire too. Is there a reason that function is wrapped in
> a unwind-protect (now in g-a-e-1)? I think it is better to handle
> whatever errors crop up during its execution instead, and if it still
> breaks users will be informed and can send a bug report.
Well, an `unwind-protect' doesn't mean that errors won't be
propagated; it just guarantees that the cleanup forms will be
executed even if the code fails. And then the error will be
signaled.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-02-07 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 15:24 Tiarnán Ó Corráin
2003-01-31 20:54 ` Simon Josefsson
2003-02-01 10:29 ` Kai Großjohann
2003-02-03 9:12 ` Niklas Morberg
2003-02-03 9:47 ` Simon Josefsson
2003-02-04 8:53 ` Niklas Morberg
2003-02-05 6:30 ` Simon Josefsson
2003-02-07 12:23 ` 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=m3y94scma1.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).