Didn’t notice this before, but there is something strange with the find_under commands:
find_under:
-
if you trigger the command with the cursor inside or right after a word, you go directly to the next occurrence of the word.
-
if you trigger the command with the cursor right before a word, the current word is only selected and you need to run the command a second time to go to the next occurrence.
find_under_prev:
The exact opposite of find_under, which is IMHO not very sensible.
-
if you trigger the command with the cursor inside or right after a word, the current word is only selected and you need to run the command a second time to go to the previous occurrence.
-
if you trigger the command with the cursor right before a word, you go directly to the previous occurrence of the word.
I expect that with the cursor before/inside/after a word, the find_under/find_under_prev commands always go to the next/previous occurrence. To first select the word, there is the find_under_expand command.
Is there a reason of the current behavior ?
startup, version: 2110 windows x64 channel: dev