From: Eli Zaretskii <eliz@gnu.org>
To: charles@aurox.ch
Cc: 32990@debbugs.gnu.org
Subject: bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc
Date: Sun, 28 Oct 2018 17:53:19 +0200 [thread overview]
Message-ID: <834ld6m5jk.fsf@gnu.org> (raw)
In-Reply-To: <m2muqyz8p5.fsf@aurox.ch> (charles@aurox.ch)
> Date: Sun, 28 Oct 2018 11:06:46 +0100
> From: charles@aurox.ch (Charles A. Roelli)
> CC: 32990@debbugs.gnu.org
>
> The following patch improves indexing of the isearch commands and
> bindings mentioned in the current docstring of isearch-forward, and
> adds an explanation in the manual for one missing command
> (isearch-query-replace-regexp). This should be one of the last
> changes before we can comfortably shorten isearch-forward's docstring.
Thanks, I have a couple of minor comments:
> +search string. You can repeat this any number of times. If you
> +overshoot, you can cancel some @kbd{C-s} characters with @key{DEL}.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I would say "cancel some @kbd{C-s} commands", not "characters".
"Cancel characters" sounds awkward and slightly confusing.
> +@kindex M-s w
> +@kindex M-s w @r{(Incremental Search)}
It is not useful to have several index entries starting with the same
string and pointing to the same place, or very close places. In this
case, I think just the first one will do.
next prev parent reply other threads:[~2018-10-28 15:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 17:58 bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc Charles A. Roelli
2018-10-08 20:07 ` Eli Zaretskii
2018-10-09 18:14 ` Charles A. Roelli
2018-10-09 18:21 ` Eli Zaretskii
2018-10-14 19:53 ` Charles A. Roelli
2018-10-15 15:02 ` Eli Zaretskii
2018-10-16 18:57 ` Charles A. Roelli
2018-10-20 9:59 ` Eli Zaretskii
2018-10-25 19:11 ` Charles A. Roelli
2018-10-28 10:06 ` Charles A. Roelli
2018-10-28 15:53 ` Eli Zaretskii [this message]
2018-10-28 17:09 ` Charles A. Roelli
2018-11-10 13:57 ` Charles A. Roelli
2018-11-10 14:05 ` Eli Zaretskii
2018-11-15 19:57 ` Charles A. Roelli
2018-11-15 20:07 ` Eli Zaretskii
2018-11-15 22:15 ` Juri Linkov
2018-11-16 8:53 ` martin rudalics
2018-11-16 16:00 ` Drew Adams
2018-11-17 9:29 ` martin rudalics
2018-11-17 21:32 ` Juri Linkov
2018-11-18 9:22 ` martin rudalics
2018-11-16 20:22 ` Charles A. Roelli
2018-11-17 21:01 ` Juri Linkov
2018-11-17 21:07 ` Juri Linkov
2018-11-18 1:49 ` Drew Adams
2018-11-18 20:24 ` Charles A. Roelli
2018-11-18 22:42 ` Juri Linkov
2018-11-19 20:14 ` Charles A. Roelli
2018-11-19 21:44 ` Juri Linkov
2018-11-20 19:49 ` Charles A. Roelli
2018-11-21 20:14 ` Charles A. Roelli
2018-11-21 22:31 ` Juri Linkov
2018-11-22 20:29 ` Charles A. Roelli
2018-11-22 21:59 ` Juri Linkov
2018-11-23 8:17 ` Eli Zaretskii
2018-11-24 11:25 ` Charles A. Roelli
2018-11-24 11:44 ` Eli Zaretskii
2018-11-24 12:51 ` Charles A. Roelli
2019-04-02 0:22 ` Noam Postavsky
2018-11-10 20:34 ` Juri Linkov
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=834ld6m5jk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32990@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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.