From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/60991 Path: news.gmane.org!not-for-mail From: Russ Allbery Newsgroups: gmane.emacs.gnus.general Subject: Re: No Gnus doesn't like the obsolete spam syntax Date: Tue, 20 Sep 2005 10:26:52 -0700 Organization: The Eyrie Message-ID: <87zmq7tztv.fsf@windlord.stanford.edu> References: <874q9yy02n.fsf@windlord.stanford.edu> <4nirwvk99d.fsf@lifelogs.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1127237398 555 80.91.229.2 (20 Sep 2005 17:29:58 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Sep 2005 17:29:58 +0000 (UTC) Original-X-From: ding-owner+m9523@lists.math.uh.edu Tue Sep 20 19:29:54 2005 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EHlu5-0003ec-Rc for ding-account@gmane.org; Tue, 20 Sep 2005 19:27:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1EHlu1-00055j-00; Tue, 20 Sep 2005 12:27:33 -0500 Original-Received: from nas01.math.uh.edu ([129.7.128.39]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1EHltY-00055e-00 for ding@lists.math.uh.edu; Tue, 20 Sep 2005 12:27:04 -0500 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas01.math.uh.edu with esmtp (Exim 4.52) id 1EHltR-0000aH-SH for ding@lists.math.uh.edu; Tue, 20 Sep 2005 12:27:03 -0500 Original-Received: from smtp2.stanford.edu ([171.67.16.125]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1EHltQ-0008Ui-00 for ; Tue, 20 Sep 2005 19:26:56 +0200 Original-Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.19.147]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id j8KHQrBu024583 for ; Tue, 20 Sep 2005 10:26:54 -0700 Original-Received: by windlord.stanford.edu (Postfix, from userid 1000) id E73A0E7CA7; Tue, 20 Sep 2005 10:26:52 -0700 (PDT) Original-To: ding@gnus.org In-Reply-To: <4nirwvk99d.fsf@lifelogs.com> (Ted Zlatanov's message of "20 Sep 2005 12:13:18 -0400") User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.4.17 (linux) X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:60991 Archived-At: Ted Zlatanov writes: > On Tue, 09 Aug 2005, rra@stanford.edu wrote: >> It took me a little bit to get the syntax right, since for some reason I >> read the manual suggestion and thought it said to replace >> gnus-group-spam-exit-processor-bogofilter >> with >> ('(spam spam-use-bogofilter)) >> literally. That just silently fails with no error message, apparently >> due to having one too many layers of parens. > Yeah... I wasn't sure about changing to the new style of configuration > for exactly this reason - backwards compatibility. I think the pain is > worth it, though, as the new format is much better IMO. Yeah, I agree that the new format is better. > Was the manual misleading in any way? I'll be glad to fix it. The only thing that was mildly misleading was this part: _WARNING_ Instead of the obsolete `gnus-group-spam-exit-processor-bogofilter', it is recommended that you use `'(spam spam-use-bogofilter)'. Everything will work the same way, we promise. I *think* that leading ' isn't actually desirable, although I'm not positive at this point. It looks like my main issue may have already been fixed, though, since I think at one point there was another level of parens. Also, the manual entry there implies that the old syntax will still work, and it didn't appear to for me. > Of course, don't forget that Gnus has three ways to set group variables, > through gnus-parameters, individual global variables, and group/topic > parameters... It's insane IMHO. I would prefer to pick one > (group/topic parameters are best I think) and provide conversion > functions from the others to it. But anyhow :) I do most everything through a combination of gnus-parameters and individual global variables, largely because most of my rules apply to whole classes of groups and editing properties on each of hundreds of groups is pretty tedious. I use all three, but the group parameters are used for special cases and overrides. (Topic parameters aren't useful as a grouping mechanism for these settings for me since I use topics to organize groups along a completely different axis.) -- Russ Allbery (rra@stanford.edu)