From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding <ding@gnus.org>
Subject: Re: nnmail-split-fancy-match-partial-words
Date: Fri, 03 Mar 2006 20:13:08 +0900 [thread overview]
Message-ID: <b4mr75jye63.fsf@jpl.org> (raw)
In-Reply-To: <slpzq2t8.fsf@esemetz.metz.supelec.fr>
>>>>> In <slpzq2t8.fsf@esemetz.metz.supelec.fr>
>>>>> Fabrice Popineau wrote:
> 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.
> - (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))
Thank you for the patch, but it seems to be better to use
"\\\\\\[.*\\\\\\]" because "\\[.*\\]" matches "[0-9]", "[a-z]",
etc. Does anyone notice other adverse effects?
> BTW, all occurences of set-file-modes should be replaced with
> gnus-set-file-modes for windows users'sake (at least under xemacs).
> - (set-file-modes filename nnmail-default-file-modes)))
> + (gnus-set-file-modes filename nnmail-default-file-modes)))
I think it should be applied anyway. mail-source.el and
mm-decode.el also use set-file-modes.
> I'm using xemacs 21.5.b21 under native windows for what it worth.
I will install those changes if no one comments within a couple
of days.
next prev parent reply other threads:[~2006-03-03 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 9:45 nnmail-split-fancy-match-partial-words Fabrice Popineau
2006-03-03 11:13 ` Katsumi Yamaoka [this message]
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=b4mr75jye63.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/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).