[HN Gopher] Vim Racer
       ___________________________________________________________________
        
       Vim Racer
        
       Author : udev4096
       Score  : 140 points
       Date   : 2024-08-25 13:12 UTC (1 days ago)
        
 (HTM) web link (vim-racer.com)
 (TXT) w3m dump (vim-racer.com)
        
       | kingkongjaffa wrote:
       | This is super fun, do you know any other vim games like this?
       | I've always wanted to vim (emacs evil mode user) but I'm not
       | exactly fast.
        
         | jrvieira wrote:
         | vimgolf.com is a classic
        
         | gnomespaceship wrote:
         | There's Vim Adventure which is more tutorial than a game bit
         | still: https://vim-adventures.com/
        
           | palata wrote:
           | Vim Adventure is great! I find it annoying that it's 25$ for
           | 6 months, because I definitely won't pay again just to
           | quickly redo one level. I think a one-time payment would be
           | more fair.
           | 
           | Or maybe if they keep adding level, we could pay per level,
           | so that the levels that have already been paid would stay
           | forever? I don't know.
        
       | daphodile wrote:
       | I just went through all the "maps," very insightful!
        
       | helix278 wrote:
       | Very nice. I would like this for Helix, and allow bringing your
       | own config!
        
         | vegabook wrote:
         | What's the latest talk on the timing for the scheme-based
         | scripting language?
        
       | ddlutz wrote:
       | 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.
        
         | lucianbr wrote:
         | It shows what the people on the leaderboard used, seems close
         | enough.
        
         | hexomancer wrote:
         | You are looking for this: https://github.com/igrigorik/vimgolf
        
         | vim_racer wrote:
         | 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!
        
         | JelteF wrote:
         | 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.
        
       | iamcreasy wrote:
       | It is very useful to be able to see how other did it though
       | leaderboard.
        
       | s1mplicissimus wrote:
       | 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 is constructed, i noticed some
       | of the top players are at 1 second, which doesn't seem humanly
       | possible to me (that would amount to < 0.05 seconds per move). my
       | assumption is they are using scripted input, which with this
       | interface will be hard to prevent. i read you are still figuring
       | out how to regulate everything, so here's an idea: if you rank
       | the leaderboard by number of keystrokes (might consider special
       | handling for shift etc.) instead of time elapsed, you will get
       | the most efficient leaders instead of the fastest ones - that way
       | scripting wouldn't help cheaters anymore.
       | 
       | All the best moving forward!
        
         | roflmaostc wrote:
         | Well you can search for the shortest command combination to
         | reach that position, at least to some extent.
        
         | omega3 wrote:
         | VimGolf does it this way.
        
           | rahen wrote:
           | It's unfortunately very broken.
        
             | wyclif wrote:
             | Do you mean vimgolf or Vim Racer?
        
       | rossant wrote:
       | It's a game you can't stop once you start.
        
         | dp-hackernews wrote:
         | Because you can't exit vim? :-)
        
           | rossant wrote:
           | You got it!
        
         | vim_racer wrote:
         | I might just have to add a :q easter egg some day.
        
       | fdlaks wrote:
       | 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
        
         | vim_racer wrote:
         | 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.
        
       | lelanthran wrote:
       | Doing `/searchterm/e` doesn't work.
       | 
       | Quite nice otherwise.
        
       | notemaker wrote:
       | I've had a similar idea on my backburner for two years, as a fun
       | project to dabble in Elixir, but this is just so much more _fun_
       | than my version which looks like an admin page that just happens
       | to have a Vim canvas on it.
       | 
       | Well done!
        
       | gtm1260 wrote:
       | I feel like I found a bug but I'm not sure - when I do
       | <line_number> then Shift +G I don't think the behavior is
       | correct.
        
         | vim_racer wrote:
         | 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?
        
       | javier_e06 wrote:
       | 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.
        
         | vim_racer wrote:
         | 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
        
           | vim_racer wrote:
           | Are there any other configurations that people want to have?
           | I can try to do a number of them manually.
        
       | ccvannorman wrote:
       | :4 does not go to line 4. Or at least, the line numbers are not
       | correct. No thanks, I'll pass.
        
         | thot_experiment wrote:
         | 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.
        
         | vim_racer wrote:
         | Another user mentioned this too. I'll be adding settings to let
         | users turn relative lines off.
        
       ___________________________________________________________________
       (page generated 2024-08-26 23:00 UTC)