Proposal: Improve keyboard navigation in text files

[SetTrend]

I feel that the current stop points used by Code for navigating through a text document using keyboard combinations CTRL + LEFT ARROW and CTRL + RIGHT ARROW, resp., are quite confusing.

Apparently, the cursor isn't moved to the next word boundary (regex anchor \b) as is done by almost any editor I know. ... Frankly, I fail trying to understand what the exact algorithm behind the current keyboard navigation behaviour in Code may be.

Can we have Code behave like Visual Studio 2015 when navigating through text files using keyboard combinations CTRL + LEFT ARROW and CTRL + RIGHT ARROW, resp.?

[joaomoreno]

ping @bpasero

[alexdima]

@SetTrend please check out the upcoming 0.10.10 where we've refurbished the word navigation

[SetTrend]

Great work. I'm looking forward to it.

Thanks! 👏

[alexdima]

@SetTrend To clarify, the navigation is refurbished, but Ctrl+Right will still go to the end of the words, and not to the beginning of words as in Visual Studio 2015.

We're tracking this in #3577 and considering making it into an editor option.

[SetTrend]

Excellent. I'm sure this'll give much comfort to Windows users when switching between applications.

Thanks for keeping up the good work! 🌻