diff options
Diffstat (limited to 'lispref')
| -rw-r--r-- | lispref/ChangeLog | 5 | ||||
| -rw-r--r-- | lispref/searching.texi | 7 |
2 files changed, 10 insertions, 2 deletions
diff --git a/lispref/ChangeLog b/lispref/ChangeLog index 970ecc4d494..ff73949f771 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -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 --git a/lispref/searching.texi b/lispref/searching.texi index d18587ccecb..4a2703fd640 100644 --- a/lispref/searching.texi +++ b/lispref/searching.texi @@ -1459,8 +1459,11 @@ corresponds to @code{(match-end @var{n})}. 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, |