From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el+ifile doesn't notice 'S x'd articles
Date: Fri, 24 Jan 2003 00:08:57 -0500 [thread overview]
Message-ID: <m3k7gvjfrq.fsf@heechee.beld.net> (raw)
In-Reply-To: <87znpuwdbk.fsf@eris.void.at> (Andreas Fuchs's message of "Tue, 21 Jan 2003 18:45:08 +0000 (UTC)")
On Tue, 21 Jan 2003, asf@void.at wrote:
>>> spam.el is beginning to feel good to use now... Could you add
>>> messages in the exit processors, so that it's clearer when spam.el
>>> routines are at work?
>> I was trying to avoid too much verbosity. I can use gnus-verbose,
>> but what messages would you suggest?
>
> I had "Reclassifying/Moving spam/ham articles...",
> "Reclassifying/Moving spam/ham articles...done.", in mind, nothing
> more. Just something that tells the user that a) spam.el is
> correctly set up and b) that emacs hasn't crashed (-:
I tried to do this - if you spot any places that need more or less
messages, let me know.
Ted
prev parent reply other threads:[~2003-01-24 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 16:37 David Z Maze
2003-01-21 16:55 ` Ted Zlatanov
2003-01-21 18:01 ` Andreas Fuchs
2003-01-21 18:40 ` Ted Zlatanov
2003-01-21 18:45 ` Andreas Fuchs
2003-01-24 5:08 ` 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=m3k7gvjfrq.fsf@heechee.beld.net \
--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).