aboutsummaryrefslogtreecommitdiffstats
path: root/lisp/subr.el
diff options
context:
space:
mode:
authorDavid Kastrup <[email protected]>2005-02-19 18:54:17 +0000
committerDavid Kastrup <[email protected]>2005-02-19 18:54:17 +0000
commitc761fd554a208d5f10467d2a484f866c49f5d685 (patch)
tree7799c767ce7a2f4d146cb11e450c2a85404da1c6 /lisp/subr.el
parent7ca4e8a10ff3b58f2af5a0a67f0f71190f3a569f (diff)
(subregexp-context-p): Fix garbled doc string by adding
quoting.
Diffstat (limited to 'lisp/subr.el')
-rw-r--r--lisp/subr.el8
1 files changed, 4 insertions, 4 deletions
diff --git a/lisp/subr.el b/lisp/subr.el
index 3d1a7203dd..252154c7b0 100644
--- a/lisp/subr.el
+++ b/lisp/subr.el
@@ -2221,10 +2221,10 @@ and replace a sub-expression, e.g.
(defun subregexp-context-p (regexp pos &optional start)
"Return non-nil if POS is in a normal subregexp context in REGEXP.
A subregexp context is one where a sub-regexp can appear.
-A non-subregexp context is for example within brackets, or within a repetition
-bounds operator \\{..\\}, or right after a \\.
-If START is non-nil, it should be a position in REGEXP, smaller than POS,
-and known to be in a subregexp context."
+A non-subregexp context is for example within brackets, or within a
+repetition bounds operator `\\=\\{...\\}', or right after a `\\'.
+If START is non-nil, it should be a position in REGEXP, smaller
+than POS, and known to be in a subregexp context."
;; Here's one possible implementation, with the great benefit that it
;; reuses the regexp-matcher's own parser, so it understands all the
;; details of the syntax. A disadvantage is that it needs to match the