From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <m.kupfer@acm.org>
Cc: 22043@debbugs.gnu.org
Subject: bug#22043: 25.0.50; search-forward and char folding
Date: Mon, 30 Nov 2015 19:33:18 +0200 [thread overview]
Message-ID: <83bnabmly9.fsf@gnu.org> (raw)
In-Reply-To: <25185.1448859182@allegro.localdomain>
> From: Mike Kupfer <m.kupfer@acm.org>
> cc: Eli Zaretskii <eliz@gnu.org>, 22043@debbugs.gnu.org
> Date: Sun, 29 Nov 2015 20:53:02 -0800
>
> > Perhaps, to be more precise, the difference is search that
> > does or does not accept general regexp patterns as _input_.
> > Those that do have "regexp" (or "-re-"?) in their name;
> > those that do not do not have it. The former do not
> > support char folding; the latter do. Is that correct (and
> > complete)?
>
> I'm afraid it's more complicated than that. If nothing else, there's
> the "word" family of search functions, which don't do character folding.
Yes, exactly. And also symbol search, etc.
I've just realized that the effect of the toggles on the search mode
is not documented in the doc strings of the toggles or in the manual,
so I added that.
next prev parent reply other threads:[~2015-11-30 17:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#22043: 25.0.50; search-forward and char folding Drew Adams
2015-11-30 4:53 ` Mike Kupfer
2015-11-30 17:33 ` Eli Zaretskii [this message]
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
2015-11-28 22:11 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
2015-11-29 20:31 ` Artur Malabarba
2015-11-29 19:10 ` 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=83bnabmly9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22043@debbugs.gnu.org \
--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).