From: Antoine Levitt <antoine.levitt@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 25562@debbugs.gnu.org
Subject: bug#25562: 25.1; isearch-forward-word first matches a non-word
Date: Sun, 29 Jan 2017 07:52:38 +0100 [thread overview]
Message-ID: <CABfD5m3_TeDyGyktQF3TK2NMJ_da8+uvt72ZNEi_195Hza0A9w@mail.gmail.com> (raw)
In-Reply-To: <87mvea3feg.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
I see, thanks for the explanation. That's still unsatisfactory to me. I
think an ideal incremental word search would just start over from the
current point each time a new character is typed (that's what most users
would expect). Then any non-insertion command would make the user "commit"
to the particular search and the incremental search proper would begin. Is
that compatible with the current design of isearch?
Best,
Antoine
On 29 Jan 2017 01:50, "Juri Linkov" <juri@linkov.net> wrote:
> merge 22589 25562
> thanks
>
> > emacs -Q
> > M-<
> > M-s w
> > it
> >
> > see that the "it" of "visit" is matched, and should not be. Subsequent
> > C-s fix this.
>
> Thanks for the report. Please see the rationale for this behavior in
> https://debbugs.gnu.org/22589
>
> Do you think the proposed change suits your case?
>
[-- Attachment #2: Type: text/html, Size: 1410 bytes --]
next prev parent reply other threads:[~2017-01-29 6:52 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 [this message]
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
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=CABfD5m3_TeDyGyktQF3TK2NMJ_da8+uvt72ZNEi_195Hza0A9w@mail.gmail.com \
--to=antoine.levitt@gmail.com \
--cc=25562@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).