So ... what, exactly, is this useful for? I mean, it graphs the keys you use in Vim in command mode, is that it?
VimGraph
11–20 of 32 posts
Re: VimGraph
#12Most of the comments here ask "what's the point?"
I'd like to submit this has no practicality from a Vim tutorial perspective. However, from the perspective of anyone wanting to learn about graph theory and who understands the concepts of typing efficiency incorporated in Vim key movements, this could be very interesting.
Kind of like many other things using Wolfram - a personal notebook that someone found interesting or useful, take it or leave it.
Re: VimGraph
#13This is one of those times when I want someone to explain the value to me. Like is this to help coding agents be more efficient? Forgive my ignorance!
The thought of forcing the AI to use vim gave me a nice chuckle. Thank you sir.
I found chatGPT to be bad at VimGolfing.
``` Here is a 35 keystrokes solution that beat your 36 keystrokes solution ! ```
And then it keeps looping in the same way if you ask it about the seahorse emoji (or sometimes just lie about the keystrokes number).
In fact that's not surprising, what is rather surprising is that some of the solutions actually work (>= 100 keystrokes)
Re: VimGraph
#14Earlier quoted context omitted.
I believe that's mostly for fun. Coding agents wouldn't need to interact via the same interfaces humans use, they'd be given a tool to read and write files and they'd be fine with that.
They're literally using diff/patch under the covers, at least the setup i'm currently using.
Did you get them working with diff syntax? I couldn't figure it out, so I just tried a bunch of agentic programs, found a few that actually worked, and it turned out they all use search/replace strings. There's probably other ways to do it but it seems basically everyone settled on that.
I've been trying that with smaller models and had to make some adjustments (e.g. they all really wanted to include the filename twice). So I just make a small tweak and bam suddenly I can edit code with small fast cheap models.
Re: VimGraph
#15Interesting. Thanks for sharing.
I'm curious about something a bit different. Given a vim buffer, and picking two caret locations in it, I'd like a tool that shows only the paths to getting there with my current Vim setup (including all the plugins).
After 10 years of using vim, I rarely use L and H. For horizontal moving it's almost always F or S (vim-sneak).
Re: VimGraph
#16[flagged]
Re: VimGraph
#17Interesting. Thanks for sharing. I'm curious about something a bit different. Given a vim buffer, and picking two caret locations in it, I'd like a tool that shows only the paths to getting there with my current Vim setup (including all the plugins). After 10 years of using vim, I rarely use L and H. For horizontal moving it's almost always F or S (vim-sneak).
More often than L and H, I use { and }, which jumps across paragraphs (i.e. blocks of lines separated by blank lines).
I've found that most of my code consists of 3-5 line blocks, and { and } feel like a nice medium-range navigation tool, because oftentimes CTRL+D jumps too far.
The downside is that both of these jumps go into the jump table, so they will clutter your CTRL+O history a bit.
But I think I'm weird in this regard.
Re: VimGraph
#18Earlier quoted context omitted.
The thought of forcing the AI to use vim gave me a nice chuckle. Thank you sir.
I found chatGPT to be bad at VimGolfing. ``` Here is a 35 keystrokes solution that beat your 36 keystrokes solution ! ``` And then it keeps looping in the same way if you ask it about the seahorse emoji (or sometimes just lie about the keystrokes number). In fact that's not surprising, what is rather surprising is that some of the solutions actually work (>= 100 keystrokes)
They should probably train LLMs to be bad at vim golf. The whole point of vim’s funky language is that human keypresses are very valuable and should not be wasted. Saving keystrokes for an LLM is a non-goal at best.
Re: VimGraph
#19> Illustrates the relationship between the maximum keystroke distance required to navigate between two letters in a text and the number of randomly inserted newlines:
I'd love to see a comparison between Vim and Kakoune or Helix.
Re: VimGraph
#20Interesting. Thanks for sharing. I'm curious about something a bit different. Given a vim buffer, and picking two caret locations in it, I'd like a tool that shows only the paths to getting there with my current Vim setup (including all the plugins). After 10 years of using vim, I rarely use L and H. For horizontal moving it's almost always F or S (vim-sneak).
More often than L and H, I use { and }, which jumps across paragraphs (i.e. blocks of lines separated by blank lines). I've found that most of my code consists of 3-5 line blocks, and { and } feel like a nice medium-range navigation tool, because oftentimes CTRL+D jumps too far. The downside is that both of these jumps go into the jump table, so they will clutter your CTRL+O history a bit. But I think I'm weird in th…
I rebound ctrl+j/k to scroll about a third or fourth of the screen (~20 lines?) as an alternative to ctrl+d.
I've been using { and } more as well. Mostly to navigate paragraphs of prose, but sometimes for code too.