Vim Racer

It's using relative line numbering, at least for me this is how I've had vim set up for the last 10 years. It makes commands like 10j easier to do because you can just look to the side and see how many lines away the target is.

Another user mentioned this too. I'll be adding settings to let users turn relative lines off.

VimGolf does it this way.

Did you use % ? I'm down to 6.5 and I'm being very clunky.

Well you can search for the shortest command combination to reach that position, at least to some extent.

I've got this feedback quite a few times, so I'm going to bump configurations up on the roadmap. I think proper vimrc configs might be impossible unless I swap out some of my libraries.

I should provide the ability to disable relative lines though

I actually think the wall clock time that is used here is a more useful metric here. Using as few keystrokes is not necessarily most "efficient" in time if you have to think longer about which ones to press.

Hmmm, thats interesting. Right now it just shows every character press, regardless of what it was to achieve.

You'd be interested in something a bit more organized, so you can see how they got specifically from one target to the next. I do have a ton on the roadmap right now, but that has been added as well!

It shows what the people on the leaderboard used, seems close enough.

You can load the leaderboard and see what keys they used. E.g. number 2 finished in 1.002s and used these keys:

ArrowRight, ArrowRight, ArrowDown, ArrowRight, ArrowUp, ArrowRight, ArrowRight, ArrowRight, ArrowDown, ArrowLeft, ArrowLeft, Shift, ArrowUp, ArrowUp, Shift, ArrowRight, ArrowRight, ArrowRight, ArrowDown, ArrowDown, ArrowLeft, ArrowUp, ArrowRight, Shift, :, 4, Enter, ArrowDown, ArrowDown, ArrowDown, ArrowLeft, ArrowUp, ArrowLeft, ArrowDown, ArrowLeft, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowUp, ArrowLeft, ArrowDown, ArrowDown, ArrowLeft, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowLeft, Escape, Shift, :, 1, 1, Enter, Shift, :, 1, 0, 0, 0, Enter, ArrowDown, ArrowDown, ArrowDown, ArrowRight, ArrowLeft, ArrowLeft, ArrowLeft, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowDown, ArrowLeft, Shift, :, 5, Enter, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowRight, ArrowRight, ArrowRight, ArrowUp, ArrowRight, ArrowRight, ArrowRight, ArrowRight, ArrowLeft, Shift, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowUp, ArrowLeft, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowDown, ArrowLeft

...

You are looking for this: https://github.com/igrigorik/vimgolf

Thats a good point! I'll have a better description by the next release.

I'm conflicted about keypress count because I really want the focus to be about speed. VimGolf does a great job of covering those types of puzzles/scenarios. The differentiator here is speed. I'm hoping that I'll be able to do some sort of data analysis on key strokes. An interesting finding might be that www is faster than f<a character>.

One of my hypothesis was that searching with 'f' and 'F' is not as efficient as simply navigating with more commong motions like w, e, h, j etc. I've already been proved wrong, Although, I should phrase it like "many top performers use 'f' and 'F'." Which would suggest that they might be fast, or using them isn't too much of a detriment

I really need to second keypress minimization as a competitive factor! One reason why Vim appeals to me is not the speed (which is great) but it's ability to minimize the keypresses needed to go somewhere, or to do something.

That may not equate to raw speed, but it does equate to pleasantness of use vis-à-vis other text editors, which matters a lot to the typing experience.

There's Vim Adventure which is more tutorial than a game bit still: https://vim-adventures.com/

vimgolf.com is a classic

I've heard that feedback before, but I couldn't quite understand what was wrong. I'd really appreciate your help in troubleshooting.

My understanding is that Shift + G should be absolute positioning, so 12G will bring you to the twelfth line.

I do deviate slightly from default VIM in that relative lines are one, so the line count starts at 0, respective to your cursor. Is there a chance that this plays into your experience of the bug?

This was also my first experience was vim, so maybe it's just realistic.

Sorry about that! Something seems to be broken with my publishing pipelines. It used to be a graceful switch. Now I have to manually invalidate a cache. Seems to only happen on some publishes.

I have the same problem. Also in Chrome it uses a lot of CPU but yeah nothing happens and pressing any buttons doesn't do anything.

Because you can't exit vim? :-)

I might just have to add a :q easter egg some day.

What's the latest talk on the timing for the scheme-based scripting language?

Thats a vim option called relative line numbers.

Try this in your local vim: set rnu

Really handy for relative movements like 5j or 12k :)

Ideally, I could fix the mousing clicking and add targets that you need to delete.

I'm actually curious who would win that race. Because you're right; mouse users have a huge advantage right now, but no one just clicks on code haha!

Oh that's a huge find thank you. I wasn't sure what was missing.

I think I'm working off a white list, so I should just be able to add that to it.

It changes every time.

That has been a tough bug to fix. From a configuration standpoint, deleting should be impossible. The VIM keybindings library seems to override that.

I do really appreciate you mentioning it though because it helps in prioritization.

probably used macro for those, since the navigation is the same every time

Downvoted by true racists