From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: new spam-marks and ham-marks parameters in spam.el
Date: Sun, 30 Mar 2003 05:06:32 +0200 [thread overview]
Message-ID: <m34r5lwo1z.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <4nptonq7pf.fsf@lockgroove.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> 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?
It shouldn't matter whether the value came from the group parameters
or the alist. Are you sure that you're using the right syntax for the
params? It's supposed to be (param . value) and not (param value)...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-03-30 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 23:04 Ted Zlatanov
2003-03-30 3:06 ` Lars Magne Ingebrigtsen [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=m34r5lwo1z.fsf@quimbies.gnus.org \
--to=larsi@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).