From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Bug: spam articles not processed
Date: 1 Dec 2004 10:36:59 -0500 [thread overview]
Message-ID: <4n7jo2m3ms.fsf@lifelogs.com> (raw)
In-Reply-To: <4nllcjnwpb.fsf@lifelogs.com> (Ted Zlatanov's message of "30 Nov 2004 11:11:28 -0500")
On 30 Nov 2004, tzz@lifelogs.com wrote:
> gnus-summary-pop-limit throws an error if there are no limits on the
> stack.
>
> I could have gone directly to the
>
> (gnus-summary-limit nil 'pop)
>
> call that gnus-summary-pop-limit does, but it seemed like a better
> idea to go through the higher-level API. As I already mentioned, I
> don't know the summary limit functionality so if anyone else thinks
> there's a better way, they are welcome to correct me.
Well, popping the summary limit makes spam.el lose track of ham
messages for me (I have the tick-mark as a ham mark). Until I figure
out what's happening, I'm disabling the summary limit pop. Any
suggestions are most welcome.
Ted
prev parent reply other threads:[~2004-12-01 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 10:03 Jan Rychter
2004-11-17 15:18 ` Ted Zlatanov
2004-11-23 21:26 ` Jan Rychter
2004-11-26 14:15 ` Ted Zlatanov
2004-11-29 1:26 ` Katsumi Yamaoka
2004-11-29 1:37 ` Katsumi Yamaoka
2004-11-29 19:03 ` Ted Zlatanov
2004-11-29 19:33 ` Reiner Steib
2004-11-30 16:11 ` Ted Zlatanov
2004-12-01 15:36 ` Ted Zlatanov [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=4n7jo2m3ms.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/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).