From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: Nocem errors block things
Date: 21 May 1997 12:01:52 +0200 [thread overview]
Message-ID: <bypvul6t4f.fsf@midget.math.ethz.ch> (raw)
In-Reply-To: Scott Blachowicz's message of Tue, 20 May 1997 09:54:10 -0700
Scott Blachowicz <scott@apple.statsci.com> writes:
> I got the same thing recently, after which I did a `M-x gnus-bug' to report
> it. However, I did forget to get a function traceback of the error, so Lars
> probably had a hard time tracking it down. Of course, now I don't have the
> offending message in our news spool any more. Maybe you could turn on
I know how to submit a backtrace.. However I was not commenting about
the fact that it barfed. The message is probably malformed. I was
sayign I didn't like that fact that Gnus stopped after MailCrypt
barfed. Now if Gnus was supposed to catch that, that was a bug and I
will submit a backrtace. However I first want to know wether it is and
if not I would like it to be that way.
Jan
next prev parent reply other threads:[~1997-05-21 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-19 22:16 Jan Vroonhof
1997-05-20 16:54 ` Scott Blachowicz
1997-05-21 10:01 ` Jan Vroonhof [this message]
1997-05-24 3:42 ` Lars Magne Ingebrigtsen
1997-05-24 9:56 ` Jan Vroonhof
1997-05-31 17:01 ` David Moore
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=bypvul6t4f.fsf@midget.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).