summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2012-03-28 01:02:53 -0700
committerGlenn Morris <rgm@gnu.org>2012-03-28 01:02:53 -0700
commitefdf29daf8de3b6c958c9390ea9bd5c0a248a5b1 (patch)
tree02d2110fb679b2d0e634a1bc08a4a34616bfe5bf
parentd14daa28e401f6079d9a656a942e4db01112d69f (diff)
downloademacs-efdf29daf8de3b6c958c9390ea9bd5c0a248a5b1.tar.gz
Comment
-rw-r--r--doc/lispref/searching.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/lispref/searching.texi b/doc/lispref/searching.texi
index 16eea349d7f..a248932b51d 100644
--- a/doc/lispref/searching.texi
+++ b/doc/lispref/searching.texi
@@ -392,6 +392,10 @@ If @code{case-fold-search} is non-@code{nil}, @samp{[a-z]} also
matches upper-case letters. Note that a range like @samp{[a-z]} is
not affected by the locale's collation sequence, it always represents
a sequence in @acronym{ASCII} order.
+@c This wasn't obvious to me, since eg the grep manual "Character
+@c Classes and Bracket Expressions" specifically notes the opposite
+@c behavior. But by experiment Emacs seems unaffected by LC_COLLATE
+@c in this regard.
Note also that the usual regexp special characters are not special inside a
character alternative. A completely different set of characters is