* gnus.texi (Splitting Mail): Mention gnus-summary-respool-trace.

(Searching for Articles): Fix.

diff --git a/texi/ChangeLog b/texi/ChangeLog
index b8ab0ea..d6b319a 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,8 @@
+2000-07-03 00:24:55  Lars Magne Ingebrigtsen  <larsi@gnus.org>
+
+       * gnus.texi (Splitting Mail): Mention gnus-summary-respool-trace. 
+       (Searching for Articles): Fix.
+
 2000-06-28  Simon Josefsson  <simon@josefsson.org>
 
        * gnus.texi (Splitting in IMAP): Update.

diff --git a/texi/gnus.texi b/texi/gnus.texi
index c2ff745..289d2e9 100644 (file)
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -5246,6 +5246,9 @@ Push the current process mark set onto the stack
 
 @end table
 
+Also see the @kbd{&} command in @xref{Searching for Articles} for how to
+set process marks based on article body contents.
+
 
 @node Limiting
 @section Limiting
@@ -8629,10 +8632,14 @@ Search through all previous articles for a regexp
 @item &
 @kindex & (Summary)
 @findex gnus-summary-execute-command
-This command will prompt you for a header field, a regular expression to
-match on this field, and a command to be executed if the match is made
-(@code{gnus-summary-execute-command}).  If given a prefix, search
-backward instead.
+This command will prompt you for a header, a regular expression to match
+on this field, and a command to be executed if the match is made
+(@code{gnus-summary-execute-command}).  If the header is an empty
+string, the match is done on the entire article.  If given a prefix,
+search backward instead.
+
+For instance, @kbd{& RET some.*string #} will put the process mark on
+all articles that have heads or bodies that match @samp{some.*string}.
 
 @item M-&
 @kindex M-& (Summary)
@@ -10944,7 +10951,10 @@ variable is @code{add-name-to-file} by default.)
 @kindex M-x nnmail-split-history
 @kindex nnmail-split-history
 If you wish to see where the previous mail split put the messages, you
-can use the @kbd{M-x nnmail-split-history} command.
+can use the @kbd{M-x nnmail-split-history} command.  If you wish to see
+where re-spooling messages would put the messages, you can use
+@code{gnus-summary-respool-trace} and related commands (@pxref{Mail
+Group Commands}). 
 
 Gnus gives you all the opportunity you could possibly want for shooting
 yourself in the foot.  Let's say you create a group that will contain
@@ -20914,6 +20924,17 @@ to be the child of the message you're commenting.
 @item
 Handle external-body parts.
 
+@item
+When renaming a group name, nnmail-split-history does not get the group
+name renamed.
+
+@item
+Allow mail splitting on bodies when using advanced mail splitting.
+
+@lisp
+  (body "whatever.text")
+@lisp
+
 @item
 Solve the halting problem.