Vim Language, Motions, and Modes Explained (2023)
1–10 of 104 posts
Re: Vim Language, Motions, and Modes Explained (2023)
#2Here come the "[..] anyway I'm happy with VSCode" comments
Re: Vim Language, Motions, and Modes Explained (2023)
#3don't forget to do a conversation class on speaking regex fluently.
Re: Vim Language, Motions, and Modes Explained (2023)
#4It's funny to see Helix mentioned, without kakoune being mentioned.
Helix is a really nifty terminal editor. It aims to be nice out-of-the-box, to have good LSP support, DAP support, and Tree-Sitter support.
Compared to vim's "action motion" keybindings, Helix goes for "motion action" (which kakoune popularised). I find this is frequently more intuitive.
Helix also has neat discoverability.. with pop-ups showing you what the available keybindings are.
Re: Vim Language, Motions, and Modes Explained (2023)
#5I've tried Vi/Vim key bindings on several occasions, but just couldn't be efficient in it. It's often touted as the "superior" form that confers benefit to those who invest time to learn it, but discussions with other coders have led me to believe this is just confirmation bias by people who prefer these key bindings.
There are people like myself who edit frequently while writing (even with in a single sentence or word), so this switching between normal and insert modes to do chunks of each operation at a time incurs a heavy cost. Yes, there is Ctrl+[ for single commands, but this is still an additional step compared to the key chord model of Emacs for instance.
Re: Vim Language, Motions, and Modes Explained (2023)
#6It's funny to see Helix mentioned, without kakoune being mentioned. Helix is a really nifty terminal editor. It aims to be nice out-of-the-box, to have good LSP support, DAP support, and Tree-Sitter support. Compared to vim's "action motion" keybindings, Helix goes for "motion action" (which kakoune popularised). I find this is frequently more intuitive. Helix also has neat discoverability.. with pop-ups showing you…
I think kakoune invented motion action keybinds, but Helix is the one popularizing it.
I love helix because it is very fast, it supports everything it needs to, and the built-in help/which key. It's what I wish vim was.
Shameless self-promotion of a discussion thread I started.
Re: Vim Language, Motions, and Modes Explained (2023)
#7Separate from the usually mentioned benefits of Vim, it cured my RSI completely.
Re: Vim Language, Motions, and Modes Explained (2023)
#8Here come the "[..] anyway I'm happy with VSCode" comments
Vim feels equivalent to a horse carrier in comparison to vscode to a modern car.
Re: Vim Language, Motions, and Modes Explained (2023)
#9Separate from the usually mentioned benefits of Vim, it cured my RSI completely.
Ditto, I switched to vim after horrible pain from eMacs’s required multi finger contortions and it helped to the point rsi hasn’t been an issue for me for 20 years.
Re: Vim Language, Motions, and Modes Explained (2023)
#10Yesterday, I used vim motions to clean up some JMH benchmark log data to a CSV. It was genuinely so useful to be able to precisely delete and replace based on regexes. I'm sure I could have done with a graphical find and replace, but it was definitely faster via vim, especially after recording macros to automate the repetitive edits.