From: Ted Zlatanov <tzz@lifelogs.com>
Subject: new spam-marks and ham-marks parameters in spam.el
Date: Wed, 19 Mar 2003 18:04:28 -0500 [thread overview]
Message-ID: <4nptonq7pf.fsf@lockgroove.bwh.harvard.edu> (raw)
The old spam-spam-marks and spam-ham-marks variables are gone. You
can now use the spam-marks and ham-marks group/topic parameters or you
can customize the gnus-parameter-ham-marks-alist and
gnus-parameter-spam-marks-alist variables. Thus, you can have special
ham or spam marks per group.
The default values for the variables correspond to the old
spam-spam-marks and spam-ham-marks settings, so the behavior should
not change at all.
I had trouble with parameters - I was getting different lists
depending on whether the setting was coming from the alist or the
group parameter! I did a conditional 1-level drop if I got one list
too many, but it seems rather strange nevertheless. All this is in
the spam-group-ham-marks function. Did I miss something about
parameter retrieval?
Ted
next reply other threads:[~2003-03-19 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 23:04 Ted Zlatanov [this message]
2003-03-30 3:06 ` Lars Magne Ingebrigtsen
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=4nptonq7pf.fsf@lockgroove.bwh.harvard.edu \
--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).