davidlgoldberg / jumpy2 Goto Github PK

When assigning codes to locations, first assign all the codes where each letter is on a different hand (e.g. go through fj, me, ic, etc. before using same handed codes like fr, gt, and dx, assuming qwerty layout) instead of just assigning them in order. This would make jumping around feel much quicker since I don't have to move the same hand twice.

Please see Jump to the End of a word.

Please see Select to the End of a word.

thanks for the extension!
if possible, locations closer to the cursor should be "easier" to jump to, sort of implementing a locality bonus.

By "easier" I mean, for example:

1. jump to close locations via one letter jumps, and only in the range "asdfghjkl"
2. jump to close locations via two letter jumps, and only in the range "asdfghjkl"

Locations farther away may use the rest of the alphabet, and also combination of lowercase/upperase letters, as is the case today.

I have researched and have some branches with several ideas for performance improvements, but it's usuable right now for decent sized files, so going ahead with release!

Hi there,
thanks for making this extension!
there is an issue that it is very difficult to see the second letter of the label. Can you please make the label sizes bigger?
i.e. in the screenshot, it's difficult to figure out which letter comes after the b ....

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 :)

When refactoring I sometimes want to move or cut a block of code.
Currently I am using the mouse or Shift + Arrows to select it.

But with Jumpy it would be so much faster.

Adding something like a modifier key to the jump which would select all text between the jump start and end would be really neat.

It'd be nice to allow the hotkeys to continue and pick up on the selection modes. (command palette works fine so it's just a binding precedence issue)

the 'f' key should also work to continue selection. Once the keybindings are worked out, 'f' should work IF #45 is already built.

I'm going to propose this simple feature which memoize or bookmarks previous successful jumps

For example
I jumped to bc, then, if I'm editing another file or in the same file, bc will jump to the same place like if I had bookmarked
Here's an implementation 45b4de8

It could be a settings that can be true or false

What do you think?

This is an odd edge case I found when my tests failed.

In the current version of VS Code, if you unfold a code block and then IMMEDIATELY open Jumpy2, the previously folded region will be missing the labels. Instead, if you first you move the cursor or click to focus on the editor it resumes working.

Please see Select to the Start of a word.