Mercurial > emacs
changeset 69413:774f0386ba3c
(Regexp Special): Use @samp for regular expressions that are not in
Lisp syntax.
| author | Luc Teirlinck <teirllm@auburn.edu> |
|---|---|
| date | Sat, 11 Mar 2006 21:23:11 +0000 |
| parents | ecc36e13e6ba |
| children | a159957988d5 |
| files | lispref/searching.texi |
| diffstat | 1 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/searching.texi Sat Mar 11 21:21:57 2006 +0000 +++ b/lispref/searching.texi Sat Mar 11 21:23:11 2006 +0000 @@ -476,7 +476,7 @@ 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 @@ @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