After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745791 - Vim : * command doesn't have a good word notion
Vim : * command doesn't have a good word notion
Status: RESOLVED DUPLICATE of bug 765889
Product: gnome-builder
Classification: Other
Component: editor
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on: 736522
Blocks:
 
 
Reported: 2015-03-07 13:52 UTC by Kevin Hagner
Modified: 2017-01-19 11:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kevin Hagner 2015-03-07 13:52:04 UTC
In Vim, the * command will find every other occurrences of the word under the cursor but in gnome-builder, the search is not including space characters that wrap the word. This means that the * command in gnome-builder is looking for substring presents inside words.

An example:
If I press the * character under the “logs” word, I will also find all words that are containing the “logs” substring, like : logsDictionary, logsStatistics, etc.
Comment 1 Ray Strode [halfline] 2015-11-10 20:35:01 UTC
so we're a little better here these days, but it's not perfect.  If you hit '*' repeatedly it does whole word searches, but if you switch to using 'n' it doesn't remember that it's a whole word search and instead does a substring search. That's because the move-search action that 'n' is bound to's word_boundaries parameter can only have two possible values: TRUE or FALSE (no way to say "wheatever was used before").

maybe it should be split off into two actions or the parameter should get changed into an enum.
Comment 2 Christian Hergert 2015-11-10 20:56:34 UTC
Switching to an enum makes sense. We can even maintain ABI (as if that mattered).
Comment 3 Alexandre Franke 2017-01-19 11:14:42 UTC
Even though this one is older, I'm closing it as duplicate of 765889 since the other one has patches and a discussion.

*** This bug has been marked as a duplicate of bug 765889 ***