Nothing elitist about it. Vim is not a modular tool that I can swap out of my mental model. Before someone says it, I've tried VS Code's vim plugin, and it sucks ass.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

Wdym? Vim is in every ide and notepad man

[–] [email protected] 1 points 9 months ago (1 children)

Certain shortcut keys in vim conflict with shortcut keys in the IDE. The flow doesn't work the same.

[–] [email protected] 0 points 9 months ago (1 children)

I don't understand how you think you will convince anyone that you can't use vim, when so many do that without problems

[–] [email protected] 0 points 9 months ago

Please avoid double negatives. I'm not quite sure of the meaning of your sentence.

If you're saying I have issues using vim if I can't use it in an IDE, no, that's not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it's fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.

If someone were to learn vim inside an IDE and develops it organically as part of their flow, it'd be fine. If you already have a lot of standalone vim flow setup in your mind, it's a problem.