# HG changeset patch
# User David Kastrup <dak@gnu.org>
# Date 1088726061 0
# Node ID a75eb408147c4307398be3ad653b1e8d6c7bf4df
# Parent  3415fedf59837b4be23a5c5e9f4db5742d883da9
(Entire Match Data): Add explanation about new
match-data behavior when @var{integers} is non-nil.

diff -r 3415fedf5983 -r a75eb408147c lispref/ChangeLog
--- a/lispref/ChangeLog	Thu Jul 01 21:03:14 2004 +0000
+++ b/lispref/ChangeLog	Thu Jul 01 23:54:21 2004 +0000
@@ -1,3 +1,8 @@
+2004-07-02  David Kastrup  <dak@gnu.org>
+
+	* searching.texi (Entire Match Data): Add explanation about new
+	match-data behavior when @var{integers} is non-nil.
+
 2004-06-24  Richard M. Stallman  <rms@gnu.org>
 
 	* commands.texi (Misc Events): Describe usr1-signal, usr2-signal event.
diff -r 3415fedf5983 -r a75eb408147c lispref/searching.texi
--- a/lispref/searching.texi	Thu Jul 01 21:03:14 2004 +0000
+++ b/lispref/searching.texi	Thu Jul 01 23:54:21 2004 +0000
@@ -1459,8 +1459,11 @@
 All the elements are markers or @code{nil} if matching was done on a
 buffer and all are integers or @code{nil} if matching was done on a
 string with @code{string-match}.   If @var{integers} is
-non-@code{nil}, then all elements are integers or @code{nil}, even if
-matching was done on a buffer.  Also, @code{match-beginning} and
+non-@code{nil}, then the elements are integers or @code{nil}, even if
+matching was done on a buffer.  In that case, the buffer itself is
+appended as an additional element at the end of the list
+to facilitate complete restoration of the match data.  Also,
+@code{match-beginning} and
 @code{match-end} always return integers or @code{nil}.
 
 If @var{reuse} is non-@code{nil}, it should be a list.  In that case,