aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2005-04-17 15:44:33 +0000
committerRichard M. Stallman <[email protected]>2005-04-17 15:44:33 +0000
commit86cf000e8409952e492ed786102af11d4017fdd3 (patch)
tree42cbf2bc1e8e1a36f4b56bd4e525b22dae3f2e7a
parentc06b447862099d804f2092fad4b5dc1b0159cc32 (diff)
(String Basics): Mention string-match; clarify.
-rw-r--r--lispref/strings.texi9
1 files changed, 5 insertions, 4 deletions
diff --git a/lispref/strings.texi b/lispref/strings.texi
index 3080270931..bfe0f1f7e1 100644
--- a/lispref/strings.texi
+++ b/lispref/strings.texi
@@ -74,10 +74,11 @@ a key sequence, you must use a vector instead of a string.
and other modifiers for keyboard input characters.
Strings are useful for holding regular expressions. You can also
-match regular expressions against strings (@pxref{Regexp Search}). The
-functions @code{match-string} (@pxref{Simple Match Data}) and
-@code{replace-match} (@pxref{Replacing Match}) are useful for
-decomposing and modifying strings based on regular expression matching.
+match regular expressions against strings with @code{string-match}
+(@pxref{Regexp Search}). The functions @code{match-string}
+(@pxref{Simple Match Data}) and @code{replace-match} (@pxref{Replacing
+Match}) are useful for decomposing and modifying strings after
+matching regular expressions against them.
Like a buffer, a string can contain text properties for the characters
in it, as well as the characters themselves. @xref{Text Properties}.