From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: spam.el is customizable now
Date: Wed, 01 Jan 2003 20:55:41 +0100 [thread overview]
Message-ID: <84r8bwzltu.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3u1gu9o3v.fsf@heechee.beld.net>
Ted Zlatanov <tzz@lifelogs.com> writes:
> The only problem I had is in making a customizable list of marks to be
> considered spam/ham marks. Right now it's a list of characters, but
> it would be better if it was a list of mark choices, with each choice
> inserting the correct character in the list. The list of marks can be
> static, but it would be perfect if it came from the authoritative Gnus
> list of marks. If anyone is interested in doing this, feel free.
Does it work to use `set'? Per told me to use it for my
site-start.el, and it works nicely. (In site-start.el, I have a
variable ls6setup which contains a list of ls6setup-foo functions, and
users can customize them to decide which parts of the setup they
want.)
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-01 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 15:58 Ted Zlatanov
2003-01-01 19:55 ` Kai Großjohann [this message]
2003-01-02 0:19 ` 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=84r8bwzltu.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).