From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22043@debbugs.gnu.org, m.kupfer@acm.org
Subject: bug#22043: 25.0.50; search-forward and char folding
Date: Sun, 29 Nov 2015 21:19:42 +0200 [thread overview]
Message-ID: <837fl0obox.fsf@gnu.org> (raw)
In-Reply-To: <c38b93a3-7fd1-439b-afc4-b3f7d4e7b100@default>
> Date: Sun, 29 Nov 2015 11:08:41 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 22043@debbugs.gnu.org
>
> Isn't it correct and sufficient to say that non-regexp
> incrementalsearch uses character folding by default?
No, because "C-s RET" actually invokes a regexp search behind the
user's back when character folding or lax-whitespace are in effect,
and the user has no way of knowing whether it invoked a regexp or
non-regexp search.
> IOW, isn't this default behavior true for all incremental
> search commands except regexp search, and only for those
> commands (no non-incremental search commands)?
No. Nonincremental vs incremental is not the issue. The issue is
whether the search function that the command employs uses regexps or
not. It is a limitation of how these features are implemented that
they absolutely require regexp search.
next prev parent reply other threads:[~2015-11-29 19:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 22:11 bug#22043: 25.0.50; search-forward and char folding Mike Kupfer
2015-11-28 23:57 ` Artur Malabarba
2015-11-29 16:33 ` Eli Zaretskii
2015-11-29 16:53 ` Artur Malabarba
2015-11-29 21:29 ` Artur Malabarba
2015-11-30 17:32 ` Eli Zaretskii
2015-11-29 16:32 ` Eli Zaretskii
2015-11-29 19:03 ` Mike Kupfer
2015-11-29 19:08 ` Drew Adams
2015-11-29 19:19 ` Eli Zaretskii [this message]
2015-11-29 20:31 ` Artur Malabarba
2015-11-29 19:10 ` Eli Zaretskii
[not found] <<15605.1448748702@allegro.localdomain>
[not found] ` <<17193.1448823812@allegro.localdomain>
[not found] ` <<c38b93a3-7fd1-439b-afc4-b3f7d4e7b100@default>
[not found] ` <<837fl0obox.fsf@gnu.org>
2015-11-29 20:41 ` Drew Adams
2015-11-30 4:53 ` Mike Kupfer
2015-11-30 17:33 ` Eli Zaretskii
2015-11-30 9:54 ` Artur Malabarba
2015-11-30 17:32 ` Eli Zaretskii
2015-11-30 20:31 ` Mike Kupfer
2015-11-30 20:51 ` Eli Zaretskii
2015-12-01 7:37 ` Andreas Röhler
2015-12-01 15:35 ` Eli Zaretskii
2015-12-01 20:30 ` Mike Kupfer
2015-12-02 14:10 ` Eli Zaretskii
2015-12-08 12:06 ` Artur Malabarba
2015-12-08 15:08 ` Mike Kupfer
2015-12-08 16:26 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fl0obox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22043@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=m.kupfer@acm.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).