From: Juri Linkov <juri@linkov.net>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: 21278@debbugs.gnu.org, rms@gnu.org
Subject: bug#21278: 25.0.50; char-fold search is a screw, and I can't see how to disable
Date: Thu, 20 Aug 2015 01:20:30 +0300 [thread overview]
Message-ID: <87a8tmyl3t.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAAdUY-JfD_Gb150YKspjfsiYVZDJyfzVOwyfpa18XT1hhYeH-g@mail.gmail.com> (Artur Malabarba's message of "Tue, 18 Aug 2015 22:48:20 +0100")
>> It is a screw that char-fold isearch treats space and NL as equivalent.
>> They do not look alike. Please disconnect them.
>
> As of 2 weeks ago, it doesn't. You can verify that by running
> (character-fold-to-regexp " ")
> The regexp it returns doesn't contain newline chars.
>
> isearch-lax-whitespace does treat space as NL, so maybe that's what
> you're seeing.
> I believe there's a bug in `isearch-search-fun-default' where even if
> you disable `isearch-lax-whitespace', isearch sometimes uses
> lax-whitespace anyway.
>
> I would have fixed this myself, but I don't quite understand what that
> code is trying to do and last time I asked for help nobody answered.
Sorry for missing your questions. ‘isearch-search-fun-default’ detects
the situation when the user is in the process of typing a word,
so it should not match incomplete words, otherwise the word search
will immediately fail and not allow the user to complete the word.
I guess this code is not necessary for char-fold search, but to
double-check I'm looking at this problem now.
next prev parent reply other threads:[~2015-08-19 22:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 5:04 bug#21278: 25.0.50; char-fold search is a screw, and I can't see how to disable Richard Stallman
2015-08-18 21:48 ` Artur Malabarba
2015-08-19 22:20 ` Juri Linkov [this message]
2015-08-19 22:59 ` Artur Malabarba
2021-09-04 7:04 ` bug#21278: char-fold isearch: space and newline Lars Ingebrigtsen
2021-09-06 3:09 ` bug#21278: char-fold isearch: space and newline still broken Richard Stallman
2021-09-06 5:59 ` Eli Zaretskii
2021-09-07 3:17 ` Richard Stallman
2021-09-07 6:19 ` Eli Zaretskii
2021-09-07 12:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 17:32 ` Juri Linkov
2021-09-10 10:28 ` Lars Ingebrigtsen
2021-09-10 10:54 ` Eli Zaretskii
2021-09-10 10:57 ` Lars Ingebrigtsen
2021-09-10 11:56 ` Augusto Stoffel
2021-09-10 13:17 ` Kévin Le Gouguec
2021-09-11 12:12 ` Lars Ingebrigtsen
2021-09-11 12:52 ` Augusto Stoffel
2021-09-13 7:26 ` Lars Ingebrigtsen
2021-09-06 8:32 ` Lars Ingebrigtsen
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=87a8tmyl3t.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=21278@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=rms@gnu.org \
/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.