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: Sun, 29 Nov 2015 18:32:41 +0200 [thread overview]
Message-ID: <83io4kojfa.fsf@gnu.org> (raw)
In-Reply-To: <15605.1448748702@allegro.localdomain>
> From: Mike Kupfer <m.kupfer@acm.org>
> Date: Sat, 28 Nov 2015 14:11:42 -0800
>
> The "Lax Search" Info node says
>
> Searches in Emacs by default perform character folding
>
> But I don't see search-forward or search-backward doing that. For
> example, in the scratch buffer of "emacs -Q" if I do
>
> ä C-p
> M-x search-forward RET a RET
>
> Emacs complains that the search failed.
I did test it before I wrote that text. Try this recipe instead:
ä C-p
C-s RET a RET
The Emacs manual doesn't advertise search-forward and search-backward,
it advertises "C-s RET" and "C-r RET" instead, which do (by default)
perform character folding (and also obey the rest of the features
described in that node).
So yes, it's an inaccuracy in the manual, but not in that sentence.
The inaccuracy is where the manual says (or was saying):
When you type ‘C-s <RET>’, the ‘C-s’ invokes incremental search as
usual. That command is specially programmed to invoke the command for
nonincremental search, ‘search-forward’, if the string you specify is
empty. (Such an empty argument would otherwise be useless.) ‘C-r
<RET>’ does likewise, invoking the command ‘search-backward’.
"C-s RET" doesn't invoke search-forward, at least not by default,
haven't been doing that for quite some time. I fixed that inaccuracy
now, thanks for pointing it out.
next prev parent reply other threads:[~2015-11-29 16:32 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 [this message]
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
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83io4kojfa.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 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.