From 1ab7aea17af854d3832cb1053377e1c52f621672 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Thu, 9 Mar 2006 01:55:20 +0000 Subject: [PATCH] (Regexp Special): Put remark between parentheses to avoid misreading. --- lispref/searching.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lispref/searching.texi b/lispref/searching.texi index b45467fbf83..88009152cc0 100644 --- a/lispref/searching.texi +++ b/lispref/searching.texi @@ -485,9 +485,9 @@ 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 -bracket, followed by a literal @samp{]}. +@code{[^][]]} consists of the complemented character alternative +@code{[^][]} (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 special and @samp{]} not. This lasts until the first unquoted -- 2.39.2