summaryrefslogtreecommitdiff
path: root/lisp
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2015-11-27 09:54:27 +0200
committerEli Zaretskii <eliz@gnu.org>2015-11-27 09:54:27 +0200
commita41cb8c4d3af3f7e542a7bdf79858385a3274d4d (patch)
treebcbc27249a0735fa5e2f3f2a58e5325f6dc61d71 /lisp
parentaf40b7689a768f8a4b931d9c655c9c8bdba9393e (diff)
downloademacs-a41cb8c4d3af3f7e542a7bdf79858385a3274d4d.tar.gz
Improve commentary in character-fold.el
* lisp/character-fold.el (character-fold-to-regexp): Move detailed description from commit log message to comments. (Bug#22019)
Diffstat (limited to 'lisp')
-rw-r--r--lisp/character-fold.el11
1 files changed, 8 insertions, 3 deletions
diff --git a/lisp/character-fold.el b/lisp/character-fold.el
index 0e156c50dde..0e063b07e72 100644
--- a/lisp/character-fold.el
+++ b/lisp/character-fold.el
@@ -117,9 +117,14 @@ regexp) and other characters are `regexp-quote'd."
(let* ((spaces 0)
(chars (mapcar #'identity string))
(out chars))
- ;; When the user types a space, we want to match the table entry,
- ;; but we also want the ?\s to be visible to `search-spaces-regexp'.
- ;; See commit message for a longer description.
+ ;; When the user types a space, we want to match the table entry
+ ;; for ?\s, which is generally a regexp like "[ ...]". However,
+ ;; the `search-spaces-regexp' variable doesn't "see" spaces inside
+ ;; these regexp constructs, so we need to use "\\( \\|[ ...]\\)"
+ ;; instead (to manually expose a space). Furthermore, the lax
+ ;; search engine acts on a bunch of spaces, not on individual
+ ;; spaces, so if the string contains sequential spaces like " ", we
+ ;; need to keep them grouped together like this: "\\( \\|[ ...][ ...]\\)".
(while chars
(let ((c (car chars)))
(setcar chars