From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: [Q]: Question on a spam variable
Date: Sat, 19 Feb 2005 15:53:41 +0100 [thread overview]
Message-ID: <plop87bragsiru.fsf@gnu-rox.org> (raw)
In-Reply-To: <4nvf8vqefy.fsf@lifelogs.com>
On 14 fév 2005, Ted Zlatanov wrote:
> I have rewritten the docsctring to:
>
> "*Group classification (spam, ham, or neither). Only meaningful
> when spam.el is loaded. If non-nil, this should be a list of
> group name regexps, associated with a classification. In spam
> groups, new articles are marked as spam on summary entry. There
> is other behavior associated with ham and no classification
> when spam.el is loaded - see the manual."
>
> Let me know if it's still unclear.
Much more better ;) Thank you for your time.
--
Hacker Wonderland Xavier Maillard| "Stand Back! I'm a programmer!"
.0. zedek@gnu-rox.orgz|
..0 (+33) 326 770 221 | Webmaster, emacsfr.org
000 PGP : 0x1E028EA5 | Membre de l' APRIL
prev parent reply other threads:[~2005-02-19 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 22:25 Xavier Maillard
2005-02-14 16:44 ` Ted Zlatanov
2005-02-16 16:31 ` Reiner Steib
2005-02-16 19:20 ` Ted Zlatanov
2005-02-19 14:53 ` Xavier Maillard [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=plop87bragsiru.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).