From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: nnmail-split-fancy-match-partial-words
Date: Thu, 09 Mar 2006 16:41:05 +0100 [thread overview]
Message-ID: <v964mny6b2.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mk6b5cnln.fsf@jpl.org>
On Wed, Mar 08 2006, Katsumi Yamaoka wrote:
>> I'll install this change, add a description to the Info, and
>> improve some descriptions about the partial-words matching,
>> maybe tomorrow[1], in both the trunk and the v5-10 branch[2].
>
> Done. Please fix funny English if any.
The first paragraph (not modified by you) "If the split is a list, the
first element of which is a string, ..." is hard to understand, IMHO.
I also think that your text could be simplified a little and we could
use a shorter term instead of `invert-match-partial-words'
e.g. `invert-partial'.
How about the following change?
--8<---------------cut here---------------start------------->8---
--- gnus.texi 09 Mar 2006 12:33:12 +0100 6.603.2.66
+++ gnus.texi 09 Mar 2006 16:35:58 +0100
@@ -14007,18 +14007,21 @@
regexp match expansion will be done. See below for examples.
@c Don't fold this line.
-@item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split} [@var{invert-match-partial-words}])
-If the split is a list, the first element of which is a string, then
-store the message as specified by @var{split}, if header @var{field}
-(a regexp) contains @var{value} (also a regexp). If @var{restrict}
-(yet another regexp) matches some string after @var{field} and before
-the end of the matched @var{value}, the @var{split} is ignored. If
-none of the @var{restrict} clauses match, @var{split} is processed.
-
-The last element @var{invert-match-partial-words} is optional. If it is
-not omitted and the value is non-@code{nil}, the match-partial-words
-behavior controlled by the @code{nnmail-split-fancy-match-partial-words}
-variable (see below) will be inverted. (New in Gnus 5.10.7)
+@item (@var{field} @var{value} [- @var{restrict} [@dots{}] ] @var{split} [@var{invert-partial}])
+The split can be a list containing at least three elements. If the
+first element @var{field} (a regexp matching a header) contains
+@var{value} (also a regexp) then store the message as specified by
+@var{split}.
+
+If @var{restrict} (yet another regexp) matches some string after
+@var{field} and before the end of the matched @var{value}, the
+@var{split} is ignored. If none of the @var{restrict} clauses match,
+@var{split} is processed.
+
+The last element @var{invert-partial} is optional. If it is
+non-@code{nil}, the match-partial-words behavior controlled by the
+variable @code{nnmail-split-fancy-match-partial-words} (see below) is
+be inverted. (New in Gnus 5.10.7)
@item (| @var{split} @dots{})
If the split is a list, and the first element is @code{|} (vertical
--8<---------------cut here---------------end--------------->8---
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-03-09 15:41 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 ` 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 ` Reiner Steib [this message]
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=v964mny6b2.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).