From: Alex Schroeder <alex@gnu.org>
Subject: Re: spam-stat-split-fancy: (wrong-type-argument stringp nil)
Date: Wed, 16 Apr 2003 11:30:58 +0200 [thread overview]
Message-ID: <87el42bxgt.fsf@gnu.org> (raw)
In-Reply-To: <gegg.m3smsivrvf.fsf@beldin.mt743742.dialup.rwth-aachen.de>
Mark Trettin <mtr-dev0@gmx.de> writes:
> I don't get any backtraces, that's my problem. It's only in the
> *Messages* Buffer (and in the echo-Area). This is what I have in the
> *Messages* Buffer:
>
> ,----
> | Debug on Error enabled
> | call-interactively: Quit
> ???
> | Loading /home/mark/.spam-stat.el (source)...done
> | Reading active file from localhost via nntp...
> | Reading active file via nnml...
> | nnml: Reading incoming mail from file...
> | Error in spam-stat-split-fancy: (wrong-type-argument stringp nil)
> `----
Yeah, I remember faintly that all errors while splitting are caught
by the code somewhere... :(
Alex.
next prev parent reply other threads:[~2003-04-16 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 5:57 Mark Trettin
2003-04-12 22:08 ` Lars Magne Ingebrigtsen
2003-04-16 7:11 ` Mark Trettin
2003-04-16 9:30 ` Alex Schroeder [this message]
2003-04-16 22:29 ` Lars Magne Ingebrigtsen
2003-04-17 5:50 ` Mark Trettin
2003-04-27 3:01 ` 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=87el42bxgt.fsf@gnu.org \
--to=alex@gnu.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).