💾 Archived View for gemini.circumlunar.space › users › supurb › 2021-01-15.gmi captured on 2022-04-29 at 12:52:59. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

the little that i know about vim

I originally didn't like Vim, but it's now my goto $EDITOR, allowing me to quickly edit text without leaving the visual context of my terminal emulator. I know enough to feel *comfortable* in Vim rather than frustrated. In fact, I'm using Vim right now. My Vim "epiphany" was caused by a StackOverflow post descibing Vim as a programming language, detailing the origin of the editor and how its commands work.

Your problem with Vim is that you don't grok vi.

After reading this, I started down an adventure of learning to edit files using solely `ed`. After this, along with light study of visual mode, Vim became pleasant to use.

Actually using ed

However, I still use Vim only for editing *text*. For code, I use VSCode. I understand that experienced Vim users can type quite efficiently, but I don't think typing speed is holding me back right now. I'd also like to think that I've invested enough time into VSCode to use it quite efficiently, although I'd rather yield than debate such a touchy subject.

I know enough Vim to be able to edit files over SSH, but realistically I rarely need to use a remote text editor for an extended period of time. I spend 99% of my time editing local files, 0.9% of my time editing over sshfs or sftp, and only 0.1% of my time using a text editor interface through SSH.

This is simply how things have worked out for me; your milage may vary.