From: Jan-Mark <jms@codersco.com>
To: Stefan Kangas <stefan@marxist.se>, Juri Linkov <juri@linkov.net>
Cc: Alan Mackenzie <acm@muc.de>, 22118@debbugs.gnu.org
Subject: bug#22118: 23.2; Hitting ^W in a search selects the wrong word.
Date: Thu, 13 Aug 2020 18:53:33 +0200 [thread overview]
Message-ID: <a8ffbf34-77c3-f3bf-d5ab-df97cfaf9c9b@codersco.com> (raw)
In-Reply-To: <CADwFkmmg=Go3fVO_8eM16UUxdgp5UDreJri3D3Th+7u4V3fEQg@mail.gmail.com>
> OK, thanks. Any objections to closing this?
I don't remember even what this was about. But ^W should not add words at the cursor if the
search failed to match. Which is different from the search failing because it is at the last
match (about to warp to the first match again).
If the word 'aapX' is not in my text, 'aap noot' is, and I search for 'aapX' it brings me to
'aap noot' with a failure notice. If I than type ^W it should not start looking for 'aapX noot'.
Just take the ^W out of the game in cases like this. I mean if 'aapX' cannot be found (even
once) why should you allow people to look for 'aapX noot'?
I still feel it is a bug, but I agree that it will not hit many people often. I have this once
every 1000 hours (estimate). So it's not a big bug. But a bug nonetheless.
If there is bigger bugs to fry, close it, if it is an easy fix (should be?) I'd say fix it first.
Regards,
--
Jan-Mark
next prev parent reply other threads:[~2020-08-13 16:53 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
[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 [this message]
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=a8ffbf34-77c3-f3bf-d5ab-df97cfaf9c9b@codersco.com \
--to=jms@codersco.com \
--cc=22118@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=juri@linkov.net \
--cc=stefan@marxist.se \
/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).