Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim Racer

vim-racer.com

Post reply on HN
Print view View original

21–30 of 87 posts

Re: Vim Racer

#21

Post by vim_racer »

gtm1260 wrote: post #20

I feel like I found a bug but I'm not sure - when I do then Shift +G I don't think the behavior is correct.

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?

Re: Vim Racer

#22

Post by vim_racer »

fdlaks wrote: post #16

This is really cool, I ran into a bug where I deleted a line that the program would have targeted in a future step which crashed it for me though

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.

Re: Vim Racer

#23

Post by vim_racer »

ddlutz wrote: post #9

Maybe i'm missing it, but I think this would be much more useful if it showed what the optimal way to navigate per-target was.

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!

Re: Vim Racer

#24

Post by JelteF »

ddlutz wrote: post #9

Maybe i'm missing it, but I think this would be much more useful if it showed what the optimal way to navigate per-target was.

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.

Re: Vim Racer

#25

Post by omega3 »

s1mplicissimus wrote: post #13

Hi, I just engraved myself in the highscore for the jpeg level with 17 seconds. What a lovely competitive game! I had great fun just "shooting from the gut" (no minmaxing, just did the movements i would do "instinctively" to get to the requested position) I particularly cherish the "show me the moves of leaderboard games" feature which hopefully can serve as an educational resource. In regards to how the leaderboard…

VimGolf does it this way.

Re: Vim Racer

#26

Post by rahen »

omega3 wrote: post #25
s1mplicissimus wrote: post #13

Hi, I just engraved myself in the highscore for the jpeg level with 17 seconds. What a lovely competitive game! I had great fun just "shooting from the gut" (no minmaxing, just did the movements i would do "instinctively" to get to the requested position) I particularly cherish the "show me the moves of leaderboard games" feature which hopefully can serve as an educational resource. In regards to how the leaderboard…

VimGolf does it this way.

It's unfortunately very broken.

Re: Vim Racer

#27

Post by javier_e06 »

sounds interesting but I don't understand what:"12 Targets (Burn Detector)" Means. What or where are the targets? I got it! Navigate to the yellow flashing square! Is fun but the numbers are relative so I can't type: :4 To go to line 4 which is the intuitive way.

Re: Vim Racer

#29

Post by vim_racer »

javier_e06 wrote: post #27

sounds interesting but I don't understand what:"12 Targets (Burn Detector)" Means. What or where are the targets? I got it! Navigate to the yellow flashing square! Is fun but the numbers are relative so I can't type: :4 To go to line 4 which is the intuitive way.

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

Re: Vim Racer

#30

Post by vim_racer »

vim_racer wrote: post #29
javier_e06 wrote: post #27

sounds interesting but I don't understand what:"12 Targets (Burn Detector)" Means. What or where are the targets? I got it! Navigate to the yellow flashing square! Is fun but the numbers are relative so I can't type: :4 To go to line 4 which is the intuitive way.

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

Are there any other configurations that people want to have? I can try to do a number of them manually.
Post reply on HN