Nice spotted. Didn't know this feature in vim.This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

Sorry for confusing comment. It's not fixed.

I just tested it and it works the same as in vim.


Feel free to reopen if it works not as expected. Thanks for bugreport.

It's not totally perfect, as it stands now. It reselects your current word every time. And due to word boundaries in GtkSourceView, something like "FooBar" will match a word that is longer like "FooBarBaz". That is something we need to fix.

(In reply to comment #3)
> I just tested it and it works the same as in vim.
> 
> 
> Feel free to reopen if it works not as expected. Thanks for bugreport.

No, it does not work as in vim. What Shift+# does in vim is select the word under the cursor and provide it to the search (adding word boundaries to the query). That way I can move thourgh every occurrences using n/N in vim. In Builder I can move between he occurrences only using Shift+#, but I know I can move thourgh occurrences on a search using the arrow keys.

What it should do is the same as in vim, launch a search with the word under the cursor.

There's no need for us to force the user to learn two differents ways of doing things (moving thourgh the occurrences of a search).

ok, I understand this point.

This has improved a bit since bug 743668 .  You can now do '#' and then use 'n' to go the next result.

This is fixed on the wip/libide branch (in test-ide-source-view). Going to mark as closed, but it will be *really* fixed once we merge into the workbench shell and then master.