@alexandrudima I'm really interested to getting this fixed. Still switching to sublime text for some tasks because of this.

Can you give me a hint in which module I could start looking for this bug?

@alexandrudima The problematic line is https://github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/find/common/findController.ts#L541. This line takes the latest cursor as start position when searching for matches.

Shouldn't it ignore empty selections and use the end of the last non-empty selection as last position when searching for matchings?

btw: when having multiple selections, Sublime Text will expand empty selections to select the word instead of looking for the next selection.

(Just a clarification)

In the case of:

abc f|oo        abc [f|oo]
abc b|ar    ->  abc [b|ar]
abc p|izza      abc [p|izza]

hitting CMD+D should select the full word the cursor is currently over, not just the same match.

Edit:
Maybe this could be done with offering a "expandSelectionToWord" action that can be called on multiple cursors?

@npx actually, it's even easier to create a plugin that replaces the cmd/ctrl+d command. In fact, I've just created one that works as I would've expected. If you're interested, you can find it here:

https://github.com/duydao/vscode-expand-selections

Really interested in an option like expandSelectionToWord too ! 😄

cmd+d (or ctrl+d on Windows) will now behave as described:

abc piz|za
abc ho|use
abc b|ar
--------------
abc [pizza]
abc [house]
abc [bar]