Hahaha so funny history! But to start with vim, everyone recommends using
vimtutor, he said nothing about this. 🤔I just stole someone else’s config that was shared as a neovim flake which I don’t customize at all because I’m scared to open neovim since I can’t seem to close it without googling. 🤣🤣
Sometimes the only way out is through :)
Hit escape to enter normal mode,
:qto quit if you don’t have any pending changes,:wqto save and quit (or Shift ZZ),:q!if you don’t care about your changes (save without exiting)If you’re interested in learning Vim, I’d recommend running
vimtutor, which should be present on most systems. But of course, the best way to learn it is to simply use it as much as you can!
Have you considered LunarVim?
The author discusses their experience with some nvim distributions. I think Kickstart.nvim is the way to go for new and veteran users of NeoVim.
The LunarVim install process can be kinda a pain to start, but I find it fills a wierd spot between neovim and vsodium – I still use
nvimfor making quick edits to files (especially in compiled languages) but still use vscode for really big multifile projects. LunarVim just takes too long to boot to be a drop-in neovim replacement, and the file explorer is too unintuitive to use for many files simultaneously, even as a longtime vim user. I like LunarVim, but I think it has its own usability niche, and I dont find myself using it as much as I’d like.Quite frankly, base neovim is still pretty functional for me, but the complexity of installing extensions just encourages me to use it as a text editor rather than an IDE, which is largely fine by me.
I recommend LunarVim for VS Code users too
I believe there is a vs code extension that turns lets you use vim modes and commands inside vs code. That might be a good first step for vs code users who are interested in learning vim.
lmao
