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 21:10:51 +0200 [thread overview]
Message-ID: <838u5goc3o.fsf@gnu.org> (raw)
In-Reply-To: <17193.1448823812@allegro.localdomain>
> From: Mike Kupfer <m.kupfer@acm.org>
> cc: 22043@debbugs.gnu.org
> Date: Sun, 29 Nov 2015 11:03:32 -0800
>
> The text in "Lax Search" now says
>
> Search commands in Emacs by default perform character folding
>
> But search-forward can be found using M-x apropos, and it is listed as
> being a command. So I think the text in the "Lax Search" node still
> needs work.
>
> Would something like the following be acceptable?
>
> The search commands that are described in "Incremental Search" and
> "Nonincremental Search" perform character folding by default, thus
> matching equivalent character sequences.
>
> If that's no good, an alternative might be to say that "Some search
> commands ... perform character folding", and to add a note along the
> lines of
>
> To determine whether character folding applies to a particular search
> command, see the Help text for that command.
I don't think such degree of precision is needed in a section whose
purpose is to describe an option that controls character folding.
With the commands that don't support character folding clearly
identified in the manual where those commands are described (and they
are only mentioned for completeness anyway, as they are not the
recommended ways of performing search), I think the manual strikes the
correct balance between being correct and still easily readable.
Thanks.
next prev parent reply other threads:[~2015-11-29 19:10 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
2015-11-29 20:31 ` Artur Malabarba
2015-11-29 19:10 ` Eli Zaretskii [this message]
[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=838u5goc3o.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.