Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Subject: gnus-mlspl won't ignore a group when directed to
Date: 16 Jan 2000 03:02:26 -0200	[thread overview]
Message-ID: <ork8laobh9.fsf@garnize.lsd.ic.unicamp.br> (raw)

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

I had failed to implement handling of `(split-spec . nil)'; it would
be considered the same as no split-spec at all.  Will someone with CVS
write access please install the following patch in the gnus CVS tree
for me?  TIA


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: nil-split-spec.patch --]
[-- Type: text/x-patch, Size: 2047 bytes --]

? nil-split-spec.patch
Index: lisp/ChangeLog
from  Alexandre Oliva  <oliva@lsd.ic.unicamp.br>
	
	* gnus-mlspl.el (gnus-group-split-fancy): Arrange that the
	behavior of (split-spec . nil) is as documented, not like no
	split-spec at all.
	
Index: lisp/gnus-mlspl.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-mlspl.el,v
retrieving revision 5.5
diff -u -r5.5 gnus-mlspl.el
--- lisp/gnus-mlspl.el	1999/12/04 01:10:50	5.5
+++ lisp/gnus-mlspl.el	2000/01/16 04:28:56
@@ -1,7 +1,7 @@
 ;;; gnus-mlspl.el --- a group params-based mail splitting mechanism
-;; Copyright (C) 1998,1999 Free Software Foundation, Inc.
+;; Copyright (C) 1998-2000 Free Software Foundation, Inc.
 
-;; Author: Alexandre Oliva <oliva@dcc.unicamp.br>
+;; Author: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
 ;; Keywords: news, mail
 
 ;; This program is free software; you can redistribute it and/or modify
@@ -134,7 +134,7 @@
 		       (memq group groups))
 		  (and (stringp groups)
 		       (string-match groups group)))
-	  (let ((split-spec (cdr (assoc 'split-spec params))) group-clean)
+	  (let ((split-spec (assoc 'split-spec params)) group-clean)
 	    ;; Remove backend from group name
 	    (setq group-clean (string-match ":" group))
 	    (setq group-clean
@@ -142,12 +142,13 @@
 		      (substring group (1+ group-clean))
 		    group))
 	    (if split-spec
-		(if (eq split-spec 'catch-all)
-		    ;; Emit catch-all only when requested
-		    (when catch-all
-		      (setq catch-all group-clean))
-		  ;; Append split-spec to the main split
-		  (push split-spec split))
+		(when (setq split-spec (cdr split-spec))
+		  (if (eq split-spec 'catch-all)
+		      ;; Emit catch-all only when requested
+		      (when catch-all
+			(setq catch-all group-clean))
+		    ;; Append split-spec to the main split
+		    (push split-spec split)))
 	      ;; Let's deduce split-spec from other params
 	      (let ((to-address (cdr (assoc 'to-address params)))
 		    (to-list (cdr (assoc 'to-list params)))

[-- Attachment #3: Type: text/plain, Size: 281 bytes --]


-- 
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them

                 reply	other threads:[~2000-01-16  5:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ork8laobh9.fsf@garnize.lsd.ic.unicamp.br \
    --to=oliva@lsd.ic.unicamp.br \
    /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).