From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2155 Path: news.gmane.org!not-for-mail From: kai.grossjohann@uni-duisburg.de (Kai =?iso-8859-1?q?Gro=DFjohann?=) Newsgroups: gmane.emacs.gnus.user Subject: Re: fancy mail splitting Date: Sun, 02 Mar 2003 13:13:19 +0100 Organization: University of Duisburg, Germany Message-ID: <844r6mrmow.fsf@lucy.is.informatik.uni-duisburg.de> References: <84znohltmy.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138668693 14137 80.91.229.2 (31 Jan 2006 00:51:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:51:33 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:16 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!p50876bc0.dip.t-dialin.NET!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: p50876bc0.dip.t-dialin.net (80.135.107.192) Original-X-Trace: fu-berlin.de 1046607202 60058736 80.135.107.192 (16 [73968]) User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.3.50 (i686-pc-linux-gnu) Cancel-Lock: sha1:cGiJNs67pU4CsKzE9F2Br6b4TK0= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2295 Original-Lines: 91 X-Gnus-Article-Number: 2295 Tue Jan 17 17:30:16 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2155 Archived-At: Poster 2000 writes: >>>>>> On Thu, 27 Feb 2003 14:50:45 +0100 >>>>>> In Message <84znohltmy.fsf@lucy.is.informatik.uni-duisburg.de> >>>>>> which is being read from gnu.emacs.gnus >>>>>> kai.grossjohann@uni-duisburg.de (Kai Großjohann) Said > >> Poster 2000 writes: >> >>> (any "mypackage@somewhere\" - "bugs-mypackage" "mypkg.list") >> >> The backslash looks bogus. > > Taking it as meaning an optional restrict then. What's that? Hm. Oh! You are referring to the fact that restricts are listed as "optional" in the documentation of nnmail-split-fancy. I thought you meant that the restrict was allowed to optionally be not fulfilled. That's weird :-) I think it should be (any "mypackage@somewhere" - "bugs-mypackage" "mypkg.list") without that backslash. > I've just been converting my normal split lists to fancy > format. Since I keep getting error when running > gnus-summary-respool-trace, I've tried creating the simplest possible > split. > > Everything to a single group. > > (setq nnmail-split-fancy "mail.in.misc" ) > The format of split-fancy is a split and the first type of split > mentioned is a string where this is the name of a group > > wrong type argument listp "mail.in.misc" This appears to be a bug in Gnus. The documentation of nnmail-split-fancy clearly says that this is an allowed value. Can you provide a backtrace? M-x toggle-debug-on-error RET, then repeat the problem. Then post that backtrace. > so I try > (setq nnmail-split-fancy '("mail.in.misc") ) > > again wrong type argument listp. Maybe this is really wrong syntax, so the error message is okay. Let's start with the simple case first, see above. > Likewise when I extend it to the full version for full filtering, > which is of the form. > > (setq nnmail-split-fancy ' > (| ( "Subject" "Mail Filter Log$" "mail.in.filters") > ( "X-RBL-Warning" "Blocked.*$" "mail.in.spam" ) > > ( "\\(To:\\|Cc:\\)" "someone@somewhere\\.com" "mail.in.someone") > "mail.in.misc")) > > This as far as I can tell is of the general format described in the > manual. That's right. It looks good. > But gnus-summary-respool-trace fails as before. I'm afraid I lost the "as before" part. Can you show it again, in what way does it fail? > Have I got the format of nnmail-split-fancy wrong, or is there a > problem in this version of oort. > > (gnus-version)"Oort Gnus v0.05" I'd always advise to upgrade -- using Oort means to live on the bleeding edge, and living on the old bleeding edge gives you all the disadvantages of the bleeding edge combined with the problems of old versions ;-) -- A preposition is not a good thing to end a sentence with.