diff options
| author | Luc Teirlinck <teirllm@auburn.edu> | 2006-03-11 21:23:11 +0000 |
|---|---|---|
| committer | Luc Teirlinck <teirllm@auburn.edu> | 2006-03-11 21:23:11 +0000 |
| commit | 2f5ff8c2ebfb2d1679aa3f20299c46bcf045688e (patch) | |
| tree | de4e45cc2cc4199da8fa184453607e39384609e9 /lispref | |
| parent | 5186ac255690c6088796ede4829f70c827e2bf10 (diff) | |
| download | emacs-2f5ff8c2ebfb2d1679aa3f20299c46bcf045688e.tar.gz | |
(Regexp Special): Use @samp for regular expressions that are not in
Lisp syntax.
Diffstat (limited to 'lispref')
| -rw-r--r-- | lispref/searching.texi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lispref/searching.texi b/lispref/searching.texi index 88009152cc0..9b80fdfd930 100644 --- a/lispref/searching.texi +++ b/lispref/searching.texi @@ -476,7 +476,7 @@ never remove the special meaning of @samp{-} or @samp{]}. So you should not quote these characters when they have no special meaning either. This would not clarify anything, since backslashes can legitimately precede these characters where they @emph{have} special -meaning, as in @code{[^\]} (@code{"[^\\]"} for Lisp string syntax), +meaning, as in @samp{[^\]} (@code{"[^\\]"} for Lisp string syntax), which matches any single character except a backslash. In practice, most @samp{]} that occur in regular expressions close a @@ -485,8 +485,8 @@ regular expression may try to match a complex pattern of literal @samp{[} and @samp{]}. In such situations, it sometimes may be necessary to carefully parse the regexp from the start to determine which square brackets enclose a character alternative. For example, -@code{[^][]]} consists of the complemented character alternative -@code{[^][]} (which matches any single character that is not a square +@samp{[^][]]} consists of the complemented character alternative +@samp{[^][]} (which matches any single character that is not a square bracket), followed by a literal @samp{]}. The exact rules are that at the beginning of a regexp, @samp{[} is |