Just hit top 30 in all the standard races - thanks so much, this was such a delightful way to practice my new Glove80 :)
Vim Racer
81–87 of 87 posts
Re: Vim Racer
#82This is fantastic! I wish there was a mode where you minimise the keypresses rather than the speed; that way the best solution is Vim golfing rather than fast hjkl'ing. Quick bug report: the character '`' appears as "Unsupported" in the leaderboard. This is very visible when following Duff's device using marks.
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.
Re: Vim Racer
#83This is fun! Keypress count, and a mode where rather than go faster you have to minimize the number of keypresses, would be fantastic additions. The game description could clarify what the "target" is.
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.
I think adding the ability to order by different columns would be good.
I'm actually not 100% sure if I can achieve that with dynamo db and my current data structure though. It has a great free tier, but the query language and limitations are very foreign to me.
If I wanted to sort by timeTaken, I had to set it to be one of the two keys. This also has the unfortunate consequence of blocking duplicate times.
It might just be my implementation that is strange, or the dynamo is significantly less featureful than an SQL server.
Re: Vim Racer
#84This game made me realize that even if I think it's sweet to code with keyboard only, using the mouse is generally faster, especially in this game where there's no back and forth to type something. However, using the mouse to navigate is flaky here, probably because of how the terminal and decorations are rendered, it lands a character to the right or left when clicking the target.
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!
Re: Vim Racer
#85I'd like to play, but the line numbers are following the cursor. Seems like a bug, but am I missing something? I'm not an experienced vim user but I'm normally able to navigate fine (albeit slowly). (Tried in Chrome and Firefox)
Just wanted to mention that I've made those settings configurable now, and it'll default to the normal vim line numbers. Feedback shifted this one up the priority list!
Re: Vim Racer
#86Earlier quoted context omitted.
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.
I think adding the ability to order by different columns would be good. I'm actually not 100% sure if I can achieve that with dynamo db and my current data structure though. It has a great free tier, but the query language and limitations are very foreign to me. If I wanted to sort by timeTaken, I had to set it to be one of the two keys. This also has the unfortunate consequence of blocking duplicate times. It might…
Just a note, I've looked into this a bit more and it's technically possible. It would just require some redundancy and extra logic to keep everything in sync.
The donate feature has a goal now to replace dynamo db with a sql db because it will make development and maintenance easier.
Re: Vim Racer
#87Earlier quoted context omitted.
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 expe…
It would be nice to be able to toggle off `:relativenumber`. Half the Vim users navigate large spaces by doing `42j`; have some thought for the other half that does `142G` :-)
Relative line numbers are finally configurable through the settings icon now