From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Subject: nnmail-split-fancy-match-partial-words
Date: Fri, 03 Mar 2006 10:45:39 +0100 [thread overview]
Message-ID: <slpzq2t8.fsf@esemetz.metz.supelec.fr> (raw)
Hi,
Id' like to draw attention on the following point. I have a rather long
nnmail-split-fancy list. I had this split rule :
("subject" "\\[ce\\]" foo.ce)
that was not working and I had much trouble in finding why. In fact,
that is because of interaction between
nnmail-split-fancy-match-partial-words and the status of [] that do not
belong to words in the default syntax table. While I'd like to retain
the default nil value for matching partial words, I'd expect also that
any regexp I put in the fancy split rule is taken for what it is.
I ended up in crudely patching nnmail-split-it in nnmail.el but that's
defintely not a clean answer to the problem. Maybe that's a limitation
of regexp/syntax tables after all.
BTW, all occurences of set-file-modes should be replaced with
gnus-set-file-modes for windows users'sake (at least under xemacs).
I'm using xemacs 21.5.b21 under native windows for what it worth.
--- nnmail.el 2006-02-01 13:51:57.000000000 +0100
+++ nnmail.el 2006-03-03 10:15:01.000000000 +0100
@@ -1436,7 +1436,10 @@
(string= ".*" (substring value -2)))
(setq value (substring value 0 -2)
partial-rear ""))
- (when nnmail-split-fancy-match-partial-words
+ (when
+ (or nnmail-split-fancy-match-partial-words
+ ;; FP: if there are backets in the sequence, don't surround with <..>
+ (string-match "\\[.*\\]" value))
(setq partial-front ""
partial-rear ""))
(setq regexp (concat "^\\(\\("
@@ -1907,7 +1904,7 @@
(let ((coding-system-for-write nnmail-file-coding-system)
(file-name-coding-system nnmail-pathname-coding-system))
(write-region start end filename append visit lockname)
- (set-file-modes filename nnmail-default-file-modes)))
+ (gnus-set-file-modes filename nnmail-default-file-modes)))
;;;
;;; Status functions
Best regards,
--
Fabrice Popineau
------------------------
e-mail: Fabrice.Popineau@supelec.fr | The difference between theory
voice-mail: +33 (0) 387764715 | and practice, is that
surface-mail: Supelec, 2 rue E. Belin, | theoretically,
F-57070 Metz | there is no difference !
next reply other threads:[~2006-03-03 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 9:45 Fabrice Popineau [this message]
2006-03-03 11:13 ` nnmail-split-fancy-match-partial-words Katsumi Yamaoka
2006-03-03 14:38 ` nnmail-split-fancy-match-partial-words Reiner Steib
2006-03-05 20:39 ` nnmail-split-fancy-match-partial-words Fabrice Popineau
2006-03-05 21:50 ` nnmail-split-fancy-match-partial-words Reiner Steib
2006-03-06 4:00 ` nnmail-split-fancy-match-partial-words Katsumi Yamaoka
2006-03-06 8:19 ` nnmail-split-fancy-match-partial-words Fabrice Popineau
2006-03-07 9:55 ` nnmail-split-fancy-match-partial-words Katsumi Yamaoka
2006-03-08 9:06 ` nnmail-split-fancy-match-partial-words Katsumi Yamaoka
2006-03-09 15:41 ` nnmail-split-fancy-match-partial-words Reiner Steib
2006-03-10 2:02 ` nnmail-split-fancy-match-partial-words Katsumi Yamaoka
2006-03-05 20:43 ` nnmail-split-fancy-match-partial-words Fabrice Popineau
2006-03-06 15:45 ` set-file-modes (XEmacs on w32) (was: nnmail-split-fancy-match-partial-words) Reiner Steib
2006-03-09 20:50 ` set-file-modes (XEmacs on w32) Reiner Steib
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=slpzq2t8.fsf@esemetz.metz.supelec.fr \
--to=fabrice.popineau@supelec.fr \
/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).