From: Juri Linkov <juri@linkov.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 25562@debbugs.gnu.org, antoine.levitt@gmail.com
Subject: bug#25562: 25.1; isearch-forward-word first matches a non-word
Date: Mon, 06 Feb 2017 01:48:21 +0200 [thread overview]
Message-ID: <877f54td16.fsf@mail.linkov.net> (raw)
In-Reply-To: <8737fvl5r0.fsf@drachen> (Michael Heerdegen's message of "Fri, 03 Feb 2017 15:16:03 +0100")
>> "While still adding characters" is not a useful qualification in
>> incremental search, because the user has no means to tell Emacs when
>> this phase is over. I think you meant to say "until the next C-s".
>
> Sure. I didn't suggest to add what I said literally that to the docs.
> I rather just wanted to point to a deficiency. Thanks for the
> clarification anyway.
Thanks for the suggestion. What do you think about this?
diff --git a/doc/emacs/search.texi b/doc/emacs/search.texi
index fa69ba4..a76141e 100644
--- a/doc/emacs/search.texi
+++ b/doc/emacs/search.texi
@@ -609,6 +609,8 @@ Word Search
so that the matching can proceed incrementally as you type. This
additional laxity does not apply to the lazy highlight
(@pxref{Incremental Search}), which always matches whole words.
+While you are typing the search string, @samp{Pending} appears in the
+search prompt until you use a search repeating key like @kbd{C-s}.
The word search commands don't perform character folding, and
toggling lax whitespace matching (@pxref{Lax Search, lax space
@@ -662,7 +664,9 @@ Symbol Search
direction of the search and the current search string; you can disable
symbol search by typing @kbd{M-s _} again. In incremental symbol
search, only the beginning of the search string is required to match
-the beginning of a symbol.
+the beginning of a symbol while you are typing the search string,
+@samp{Pending} appears in the search prompt until you use a search
+repeating key like @kbd{C-s}.
To begin a nonincremental symbol search, type @kbd{M-s _ @key{RET}}
for a forward search, or @kbd{M-s _ C-r @key{RET}} or a backward
next prev parent reply other threads:[~2017-02-05 23:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 11:23 bug#25562: 25.1; isearch-forward-word first matches a non-word Antoine Levitt
2017-01-29 0:29 ` Juri Linkov
2017-01-29 6:52 ` Antoine Levitt
2017-01-30 0:30 ` Juri Linkov
2017-01-30 8:12 ` Antoine Levitt
2017-01-30 23:24 ` Juri Linkov
2017-01-31 3:28 ` Eli Zaretskii
[not found] ` <CABfD5m0NxLQ5rbfXcXvxXLDK6c_88Rzsu-bwRj8gJNdh3cinSw@mail.gmail.com>
[not found] ` <CABfD5m1wB_z3aLsW_vOj0Vx6+1H48bUeWs46ORW0fFBUsNB0ew@mail.gmail.com>
2017-01-31 7:57 ` Antoine Levitt
2017-01-31 15:38 ` Eli Zaretskii
2017-02-01 0:44 ` Juri Linkov
2017-02-09 23:28 ` Juri Linkov
2017-02-14 23:28 ` Juri Linkov
2017-01-31 16:45 ` Michael Heerdegen
2017-01-31 16:51 ` Michael Heerdegen
2017-02-01 0:38 ` Juri Linkov
2017-02-01 17:51 ` Michael Heerdegen
2017-02-02 0:51 ` Juri Linkov
2017-02-02 21:07 ` Michael Heerdegen
2017-02-03 11:04 ` Michael Heerdegen
2017-02-03 13:06 ` Eli Zaretskii
2017-02-03 14:16 ` Michael Heerdegen
2017-02-05 23:48 ` Juri Linkov [this message]
2017-02-07 20:02 ` Michael Heerdegen
2017-02-09 22:35 ` 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
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=877f54td16.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=25562@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--cc=michael_heerdegen@web.de \
/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).