From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Bug: spam articles not processed
Date: 17 Nov 2004 10:18:27 -0500 [thread overview]
Message-ID: <4n7jokbj24.fsf@lifelogs.com> (raw)
In-Reply-To: <m2y8h0dc6s.fsf@tnuctip.rychter.com> (Jan Rychter's message of "Wed, 17 Nov 2004 02:03:55 -0800")
On Wed, 17 Nov 2004, jan@rychter.com wrote:
> It seems that articles marked as spam will not be processed upon group
> exit if I narrow the summary buffer in the meantime.
>
> To replicate:
>
> enter a summary buffer
> mark some spam articles
> narrow the summary (by doing for example "/ a")
> press "q"
> observe the spam articles just sitting there marked as read
I am not familiar with limits, so would it work to call
gnus-summary-pop-limit with universal-argument or is there a better
way to do it?
Ted
next prev parent reply other threads:[~2004-11-17 15:18 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 [this message]
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
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=4n7jokbj24.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@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).