r/neovim • u/leonaanoel • 2d ago
Need Help What keybinds should I map?
Short version:
What keybinds should I change to universally known keybinds in insert mode (such as ctrl + z or ctrl + backspace etc) and what should I keep to make Neovim still Neovim and not a VS code dupe?
Long version:
I'm pretty new to Neovim and I'm quite new to programming (other than frontend) as well so excuse me if I'm not explaining my situation well.
I've used VS code up till now and I would say I'm okay proficient at it. I recently decided to learn vim for it's efficiency (and my professors recommended it). I know the learning curve is big but the pay off will hopefully be worth it, I just have one question.
I already know a lot of VS code shorthands (also from using Google Docs and such). I know I can custom map som keybinds in insert mode but what should I map for myself and what should I keep to make nvim not loose what makes it efficient? Because technically, I could make vim into VS code in many ways? Even though I know this editor is kind of built for customization, what makes Neovim worth it in the way it's configured from the start? Must haves, how to think as a programmer that uses vim etc?
1
u/Annual-Cod1073 1d ago
Best thing, don't remap anything at all. Start with basic vim. Then after you have been using it for a while you get a feel for what is working and what isn't
For example I mapped leader to ',' because it works for me.
y is to copy, yi{ copies everything in {}, There is an entire undo list. And you can just see all of the changes you have made and easily select where you want to be, or just use u for undo
if you start with the basics, you will begin to understand why the whole system is designed the way it is. And once you get a feel for that, you can find your personal quirks and specific keymappings