From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Juri Linkov <juri@linkov.net>, emacs-devel <emacs-devel@gnu.org>
Cc: Dima Kogan <dima@secretsauce.net>, 21164@debbugs.gnu.org
Subject: bug#21164: 25.0.50; char-fold search broken for multi-line searches (sometimes)
Date: Wed, 5 Aug 2015 19:16:22 +0100 [thread overview]
Message-ID: <CAAdUY-JAxetZA=0moKDUbmSiMbDhymdiKbyrHEeqmXLe+fCrdQ__16717.900746926$1438798641$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <CAAdUY-JnYUaYhyUgeAS8b3dbZ2HXZULkjnMA+4Fz4HHTZgZ_hg@mail.gmail.com>
There is some logic in `isearch-search-fun-default' that I don't quite
understand, and it's giving me trouble.
The following expression is used to decide whether lax-whitespace
matching should be used.
;; Use lax versions to not fail at the end of the word while
;; the user adds and removes characters in the search string
;; (or when using nonincremental word isearch)
(let ((lax (not (or isearch-nonincremental
(null (car isearch-cmds))
(eq (length isearch-string)
(length (isearch--state-string
(car isearch-cmds))))))))
...)
I don't understand the purpose of the last clause `(eq (...) (...))'.
For me, the only effect that it has is to disable lax while isearch is
looking for matches beyond the current one.
For instance, here's what happens with me:
1. Type C-s SPC to start isearching for a space.
2. All of the clauses evaluate to nil, and the `isearch-word' function
is called with LAX being t (all good).
3. Immediately (without me typing anything), isearch will start
looking for the next match, but this time the last clause will
evaluate to t. So the `isearch-word' function will be called with LAX
being nil, and some of the upcoming matches will be missed.
4. Step 3 is repeated to find more matches, always with lax being nil.
next prev parent reply other threads:[~2015-08-05 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 4:06 bug#21164: 25.0.50; char-fold search broken for multi-line searches (sometimes) Dima Kogan
2015-08-02 20:40 ` Juri Linkov
2015-08-05 17:20 ` Artur Malabarba
2015-08-05 18:16 ` Artur Malabarba
2015-08-05 18:36 ` Drew Adams
2015-08-05 19:35 ` Artur Malabarba
2015-08-05 18:16 ` Artur Malabarba [this message]
2015-08-09 9:00 ` Artur Malabarba
2015-08-13 22:46 ` Dima Kogan
2015-08-14 16:39 ` Artur Malabarba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAdUY-JAxetZA=0moKDUbmSiMbDhymdiKbyrHEeqmXLe+fCrdQ__16717.900746926$1438798641$gmane$org@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=21164@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.