`nnmail-split-fancy' regexp

["Petersen Jens-Ulrik (NRC/Tokyo)" <jens-ulrik.petersen@nokia.com>]

I found the restriction that string VALUE regexp's should match to
whole words too restrictive...


1999-06-24  Jens-Ulrik Petersen <jens-ulrik.petersen@nokia.com>

	* nnmail.el (nnmail-split-fancy): Update docstring to reflect
	following change: ie that a VALUE need no longer match complete
	words.
	(nnmail-split-it): Change regexp so that VALUE doesn't have to
	match a whole word.  This makes it possible to match for example
	<user@some.domain>.


--- nnmail.el~	Thu Jun 24 17:15:03 1999
+++ nnmail.el	Thu Jun 24 17:15:03 1999
@@ -306,8 +306,8 @@
   the buffer containing the message headers.  The return value FUNCTION
   should be a split, which is then recursively processed.
 
-FIELD must match a complete field name.  VALUE must match a complete
-word according to the `nnmail-split-fancy-syntax-table' syntax table.
+FIELD must match a complete field name.  VALUE is matched
+according to the `nnmail-split-fancy-syntax-table' syntax table.
 You can use \".*\" in the regexps to match partial field names or words.
 
 FIELD and VALUE can also be lisp symbols, in that case they are expanded
@@ -1147,11 +1147,11 @@
 			     (if (symbolp field)
 				 (cdr (assq field nnmail-split-abbrev-alist))
 			       field)
-			     "\\):.*\\)\\<\\("
+			     "\\):.*\\)\\("
 			     (if (symbolp value)
 				 (cdr (assq value nnmail-split-abbrev-alist))
 			       value)
-			     "\\)\\>")))
+			     "\\)")))
 	(push (cons split regexp) nnmail-split-cache)
 	;; Now that it's in the cache, just call nnmail-split-it again
 	;; on the same split, which will find it immediately in the cache.