(subregexp-context-p): Fix garbled doc string by adding

quoting.

2 files changed, 9 insertions, 4 deletions

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index b4dc87bb39a..fe1947e1247 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2005-02-19  David Kastrup  <dak@gnu.org>
+
+        * subr.el (subregexp-context-p): Fix garbled doc string by adding
+        quoting.
+
 2005-02-19  Jay Belanger  <belanger@truman.edu>
 
         * calc/calc-math.el (calc-arctan, calc-tanh, calc-arctanh):
diff --git a/lisp/subr.el b/lisp/subr.el
index 3d1a7203dd0..252154c7b0f 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