From: Alan Mackenzie <acm@muc.de>
To: jms@codersco.com
Cc: 22118@debbugs.gnu.org
Subject: bug#22118: 23.2; Hitting ^W in a search selects the wrong word.
Date: 10 Dec 2015 09:25:50 -0000 [thread overview]
Message-ID: <20151210092550.6224.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.1705.1449600970.31583.bug-gnu-emacs@gnu.org>
Hello, Jan-Mark.
In article <mailman.1705.1449600970.31583.bug-gnu-emacs@gnu.org> you wrote:
> To reproduce this bug create a file that ends in the last 7 lines in
> this message (it will work if you open this message in emacs).
> Put the cursor at the first ''aap'' (line 2) hit ^S^W^W (''aap_noot'' at
> line 2, now is highlighted). Hit ^S^S^S (Failing the I-search since the last
> ''aap_noot'' (at line 6) has been reached, call this 'last-occurrence' state).
> Now hit ^W^W^W^W . Somewhere the state of 'last-occurrence' and add more
> to the search string conflict, because it adds ''_aap'' for every ^W and
> the edit window is not being updated.
I can confirm this behaviour is still present in the latest development
sources.
> Note that if you are not in 'last-occurrence' state, there is no
> problem, even at the last line. This bug only manifests itself if ^S has
> been hit until it shows "Failing the I-search" in the minibuffer.
Why is this behaviour a bug? I think that the effect of ^W in
"last-occurrence" state is probably undefined in the manual. Adding
"_aap" to the search string for each ^W does give the user feedback that
the ^W has actually been received and processed.
What do you think should happen in these circumstances? Does the current
behaviour actually give you problems?
> Regards,
> Jan-Mark
> 1 miesmiesmies
> 2 aap_noot_mies
> 3 miesmiesmies
> 4 aap_noot_does
> 5 miesmiesmies
> 6 aap_noot_aap
> 7 miesmiesmies
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2015-12-10 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 17:54 bug#22118: 23.2; Hitting ^W in a search selects the wrong word jms
[not found] ` <mailman.1705.1449600970.31583.bug-gnu-emacs@gnu.org>
2015-12-10 9:25 ` Alan Mackenzie [this message]
[not found] ` <56694D83.3080902@codersco.com>
2015-12-10 12:10 ` Alan Mackenzie
2015-12-10 13:07 ` Jan-Mark
2015-12-11 22:54 ` Juri Linkov
2020-08-12 3:33 ` Stefan Kangas
2020-08-12 23:58 ` Juri Linkov
2020-08-13 1:22 ` Stefan Kangas
2020-08-13 16:53 ` Jan-Mark
2020-08-29 16:48 ` Stefan Kangas
2020-10-11 3:05 ` Lars Ingebrigtsen
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=20151210092550.6224.qmail@mail.muc.de \
--to=acm@muc.de \
--cc=22118@debbugs.gnu.org \
--cc=jms@codersco.com \
/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).