From: Antoine Levitt <antoine.levitt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25562@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#25562: 25.1; isearch-forward-word first matches a non-word
Date: Tue, 31 Jan 2017 08:57:37 +0100 [thread overview]
Message-ID: <CABfD5m1zHsbCp+6CVSJbL03hDe+Och8jRACNKF_yum811JKWMw@mail.gmail.com> (raw)
In-Reply-To: <CABfD5m1wB_z3aLsW_vOj0Vx6+1H48bUeWs46ORW0fFBUsNB0ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
I agree it's an ill defined problem ; but then, so is isearching for
foo\|bar.
I disabled the beeping and screen flashing, so it doesn't bother me, but I
get the point.
In the end, it's mostly a matter of personal convenience. The patched
behavior suits me better, and seems more consistent with the way regexp are
handled.
Best,
Antoine
On 31 Jan 2017 04:29, "Eli Zaretskii" <eliz@gnu.org> wrote:
> From: Juri Linkov <juri@linkov.net>
> Date: Tue, 31 Jan 2017 01:24:07 +0200
> Cc: 25562@debbugs.gnu.org
>
> You can try yourself using the minimal patch below that demonstrates your
idea.
>
> But from what I see, it's not too good, using the recipe from your top
post:
>
> emacs -Q
> M-<
> M-s w
> i
>
> After typing the letter “i”, isearch fails, beeps, flashes the screen,
> with a clear indication that something went wrong. This is more confusing
> for a user, because now a user has to stop and think about what is wrong.
I think this is a consequence of the simple fact that "word search"
and "incremental search" contradict each other: as long as "the word"
was not fully specified, searching for it incrementally is not a
well-defined operation.
[-- Attachment #2: Type: text/html, Size: 1935 bytes --]
next prev parent reply other threads:[~2017-01-31 7:57 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 [this message]
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=CABfD5m1zHsbCp+6CVSJbL03hDe+Och8jRACNKF_yum811JKWMw@mail.gmail.com \
--to=antoine.levitt@gmail.com \
--cc=25562@debbugs.gnu.org \
--cc=eliz@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).