From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Unable to customize group in very recent Oort
Date: Mon, 06 Jan 2003 14:49:10 -0500 [thread overview]
Message-ID: <4ny95y5aa1.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <86wulirxo7.fsf@asfast.com> (Lloyd Zusman's message of "Mon, 06 Jan 2003 12:32:56 -0500")
On Mon, 06 Jan 2003, ljz@asfast.com wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Looks like the spam additions to gnus.el may be a problem, but it
>> hasn't been an issue for me at all. Do you have an existing
>> spam-contents parameter that may be the problem? Do you load
>> spam.el? (although that shouldn't matter) Can anyone else verify
>> this problem?
>
> I don't load spam.el, and spam-contents is not explicitly set. I
> checked spam-contents, and it's indeed set to nil (its default
> value).
>
> Could this problem stem from the fact that I don't use spam.el at
> all, but that something newly added to Oort depends on it?
I don't think anything in gnus.el, where the group parameters are,
depends on the spam.el code.
It looks like the parameters code was trying to evaluate the value of
nil as a function, in some way related to the :args parameter to
gnus-define-group-parameter. But I don't use the :args parameter so
I'm not sure why that's happening.
Can you try removing the two spam-related gnus-define-group-parameter
invocations and the related code in gnus.el (lines 1747-1874, from my
comment about adding spam parameters to
gnus-group-uncollapsed-levels)?
Also, do you get this error on a new group? Is there anything in the
group parameters (`G p')?
Thanks
Ted
next prev parent reply other threads:[~2003-01-06 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 9:27 Lloyd Zusman
2003-01-04 21:32 ` Ted Zlatanov
2003-01-06 17:32 ` Lloyd Zusman
2003-01-06 19:49 ` Ted Zlatanov [this message]
2003-01-13 20:42 ` Ted Zlatanov
2003-01-07 16:27 ` Lloyd Zusman
2003-01-07 19:38 ` Ted Zlatanov
2003-01-07 19:53 ` Lloyd Zusman
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=4ny95y5aa1.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@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).