Live data from Hacker News

Vim Language, Motions, and Modes Explained (2023)

ssp.sh

81–90 of 104 posts

Re: Vim Language, Motions, and Modes Explained (2023)

#81

Earlier quoted context omitted.

You can absolutely change the keybindings, vim is programmable.

Yes, but I meant that in the sense that when you change vim, it's no longer the vim that ships with Linux distros. It stops being the universal tool and starts becoming your custom text editor,and to me the biggest advantage of vim is how you're going to encounter it everywhere.

Doesn't everyone customise their editor(s), to a lesser or greater extent?

Re: Vim Language, Motions, and Modes Explained (2023)

#86

The dudes in the https://ytch.xyz Programming channel display their vim editors with all kind of plugins that make me jealous. Pure fireworks. There is a plugin feature that enhances the line number where your cursor is located in the leftmost column for line numbers and looks super cool. I wish I knew the name of that plugin/feature since I don't want to go into the trial an error. I also use the vim plugin for Ecli…

> There is a plugin feature that enhances the line number where your cursor is located in the leftmost column for line numbers and looks super cool.

You mean

  :set relativenumber

Re: Vim Language, Motions, and Modes Explained (2023)

#87
post #11

Earlier quoted context omitted.

I use both Vim and Emacs, extensively, so I'd just like to share my experience with mode switching in Vim. Personally, I don't find Vim mode switching to be much of a problem while editing text. It has become muscle memory to stay in normal mode by default. After any insert-mode operation, I instinctively return to normal mode. It's just a habit at this point. Take, for example, writing a for loop. I might type: for…

I think one (often forgotten) good advice to get used to the mode-switching is to move the ESC key to Capslock on the keyboard. It's tedious to learn to always go to the ESC key, upper left of the keyboard. Capslock is available from home row, and you should probably not use CAPSLOCK anyway, it's a bad practice. Put ESC key there instead and vim becomes wayyyyyyyy more ergonomic.

I’d recommend taking it even further and mapping capslock to escape when pressed by itself and CTRL when held in sequence with another key.

Re: Vim Language, Motions, and Modes Explained (2023)

#88

One of the problems is that vim is so entrenched with the QWERTY layout that any shortcut is too cumbersome in colemak

I've used colemak and vim (well kakoune nowadays) for over a decade. The only change I've needed is changing : to ,

Re: Vim Language, Motions, and Modes Explained (2023)

#89
post #23

Here come the "[..] anyway I'm happy with VSCode" comments

I've grown up on vi and later emacs, but VSCode is no joke. It does almost everything, and most of it better, and more intuitively. There's no reason to torture yourself with counting characters, words or lines in order to get the delete command correct in one go.

That's such an overtly bad characterisation of Vim editing that I can't take your reply seriously.

Re: Vim Language, Motions, and Modes Explained (2023)

#90

Earlier quoted context omitted.

You can absolutely change the keybindings, vim is programmable.

Yes, but I meant that in the sense that when you change vim, it's no longer the vim that ships with Linux distros. It stops being the universal tool and starts becoming your custom text editor,and to me the biggest advantage of vim is how you're going to encounter it everywhere.

Okay, but that's true of anything? If you customize the shortcuts in an IDE, then you are also no longer running the defaults.
Post reply on HN