I have several ideas for improving "accuracy". In the mean time I have included a conversation from the marketplace that fast forwarded some of this, by simply improving the regex (something I hadn't really attacked since the Atom version :-\ )
I have been using a newer regex for ~2 weeks and really love it so far. I will either change the default regex pattern (in the config) OR add it to the README.md
etc
Thanks Tetsuo Rulin for steering me in this direction (https://marketplace.visualstudio.com/items?itemName=DavidLGoldberg.jumpy2&ssr=false#review-details):
One of the best VSCode extensions. Makes navigating so much easier.
My recommendation to other users is to instead of using the default regex pattern which is ([A-Z]+([0-9a-z])*)|[a-z0-9]{2,} which highlights the beginning of every word, simply use the ... regex pattern which highlights every 3 letters and in my opinion that's even more precise and makes navigation even faster, even though you can't always navigate to the beginning of the word, you can navigate to pretty much any part of your code within the distance of 0-2 characters, and that's for symbols too, not just words.
Edit:
Yep, I suggested ...
but I think that's the same as .{3}
. I tried something similar to [^\s]{1,3}
but the problem is that not all matches are the same length so there are visual overlaps between the matches and it's kinda janky. I find ...
works perfectly for me.
And you have guessed correctly haha, I do use neovim for vscode, but I use it non-traditionally since I'm very new to it and most of the time I'm in insert mode but that's also because I made some cool shortcuts and modifications that allow me to move quickly in insert mode. I disabled the default caps-lock action in my OS, and basically I have caps-lock + i,j,k,l shortcut as up, left, down, and right, so my right hand doesn't have to move to the arrow keys. And I even made caps-lock+ijkl work with shift and also with ctrl and alt so I can also select text with ijkl and also move by full words, not just by character. Pair this with jumpy2, and I'm pretty damn fast :D I basically just jump to a word and use shift+alt+L to select the whole word, or shift+alt+LL to select quotes or bracket content, or caps+shift+L to select a character right.
And mine:
Thanks for the awesome review/feedback!!!
I have a few ideas of how to improve this "accuracy" in general.
In the short term, I might add this and some others to the README.md or maybe to the settings/config as well.
Also, I am curious, do you use one of the vims for VSC?
[EDIT] ...I hadn't played with this regex/accuracy stuff in quite a while, are you suggesting:
.{3}
....?
I just tried that and it's kind of nice!
I just fumbled for a few mins and got:
[^\s]{1,3}
<--- Pretty great so far!?
I am going to use that for a while to see how it goes! Thanks for getting my butt moving on the accuracy again!
These variants are particularly sufficient for vimmers where quick adjustments left and right are trivial.
BTW, some {2}
variants are probably an option for some of these too...if you're a robot! Who knows maybe a bunch of people prefer it that way too. (Which is why the regex has always stuck around)
EDIT:
I missed your edit, I think (lol, the edit trick is weird going to switch to a github issue here:
#60
Please chime in over there :)