From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 22043@debbugs.gnu.org, m.kupfer@acm.org
Subject: bug#22043: 25.0.50; search-forward and char folding
Date: Tue, 01 Dec 2015 17:35:28 +0200 [thread overview]
Message-ID: <83fuzmkwqn.fsf@gnu.org> (raw)
In-Reply-To: <565D4E2E.20001@easy-emacs.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, Mike Kupfer <m.kupfer@acm.org>,
> Drew Adams <drew.adams@oracle.com>
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> Date: Tue, 1 Dec 2015 08:37:18 +0100
>
> AFAIU it should go out there completely, being moved into a later section, where the refining stuff resides.
It is explained in a section dedicated to "lax search", where other
kinds of non-literal matching are described. I think that bringing
this stuff together in a single section makes it easier to describe,
as the features are similar with similar toggles.
> Understand char-folding as a special form of regexp-search.
This is the current implementation. But a user manual should not be
driven by implementation, it should be driven by user-level POV, where
features can be similar even though their implementations are very
different.
> IMO it isn't worth to give it a such prominent focus and distracting from more important stuff.
It doesn't get any prominent focus. Please take a look at the manual:
this is described only _after_ we've covered incremental and
non-incremental search, word search, symbol search, and regexp
search. It's actually quite close to the end of the chapter, just
before we describe replace commands.
> And it should be off by default.
This is not really relevant to documentation, which is the subject of
this bug report.
next prev parent reply other threads:[~2015-12-01 15:35 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
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 [this message]
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=83fuzmkwqn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22043@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
--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).