From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: pgnus-0.31: invoke external MIME stuff
Date: 29 Sep 1998 14:57:47 +0200 [thread overview]
Message-ID: <byiui7yt2s.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Tue, 29 Sep 1998 10:49:14 GMT"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I don't think it's worth it. Ignoring all errors when base64-decoding
> is OK.
Personally think that these error mechanisms are highly underused in
Emacs, which might be due to fact that FSF does not have these
convenience functions. This what the reason I made it is a patch. Then
you wouldn't have to do any work.
This is not the first time that bugs were hard
to find because of the
(condition-case ()
;;
(error nil))
idiom. Could you at the very least print the error message so that you just
have converted it in a non-fatal error. FWIW It might be very
interesting to know that a base64 encoded part was malformed.
Jan
next prev parent reply other threads:[~1998-09-29 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-23 15:39 Kai Grossjohann
1998-09-23 15:47 ` Lee Willis
1998-09-23 16:44 ` Kai Grossjohann
1998-09-23 16:10 ` Shenghuo ZHU
1998-09-23 16:43 ` Kai Grossjohann
1998-09-23 18:55 ` Matt Armstrong
1998-09-23 18:56 ` Jan Vroonhof
1998-09-23 22:21 ` Lars Magne Ingebrigtsen
1998-09-24 10:03 ` Jan Vroonhof
1998-09-24 17:13 ` Lars Magne Ingebrigtsen
1998-09-25 11:15 ` Jan Vroonhof
1998-09-25 13:58 ` Simon Josefsson
1998-09-25 14:17 ` Alan Shutko
1998-09-25 15:59 ` Hrvoje Niksic
1998-09-26 18:11 ` Jan Vroonhof
1998-09-29 10:43 ` Lars Magne Ingebrigtsen
1998-09-29 12:57 ` Jan Vroonhof [this message]
1998-10-01 2:39 ` Lars Magne Ingebrigtsen
1998-10-01 9:01 ` Jan Vroonhof
1998-10-01 9:12 ` Lars Magne Ingebrigtsen
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=byiui7yt2s.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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).