Vim VS vimrc

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

This post is all over the place. What are you asking? What problem exactly did you have with the https://github.com/vscode-neovim/vscode-neovim (ensure that you did not install https://github.com/VSCodeVim/Vim , which people often confuse with the other).

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...

There is also VSCodeVim extension: https://github.com/VSCodeVim/Vim which afaik does not use any external programms.

We're all biased here because you're asking in a neovim community. You should ask in a helix community but I think they'll also agree that you should learn vim first. Neovim and vim are the same in terms of modal editing. You may try vscodevim so that it doesn't change too much of your workflow and you can focus on the basic movement. And also you don't need to think about the neovim plugin ecosystem for now until you're comfortable with vanilla vim movement. For jetbrains products there are vim binding emulators too so it's more universal. I use vim emulator in intellij.

there are several vimrc files: https://github.com/amix/vimrc

Vim with https://github.com/amix/vimrc

If you want my five cents, then I would say that using something like https://github.com/amix/vimrc without fully understanding the consequences, is a bad idea. And instead you should focus on the basics of vim, vimtutor followed by :h user-manual.

Sorry can't have a GIF with a post. So I recently installed jedi-vim and I'm using it along with this vim-rc https://github.com/amix/vimrc. It will autocomplete in strange ways and I will have to do ctrl + L to redraw. Has anyone else experienced this?

Archcraft's vim uses this vimrc which adds a lot of plugins including some for improving appearance, so it's more suited for a terminal emulator than a tty.

Or if you want something very minimal, just for easier editing experience when connected to server, try just a simple preconfigured vimrc file, where you can comment and uncomment stuff that you might need. I use amix as base for my own vimrc file.

Vim with Awesome vimrc. https://github.com/amix/vimrc

Michael: I spent a long time getting my vimrc configured properly and all the right plugins and the language server protocols. And I just tried VS Code, and it just worked. I thought, how many hours could I have saved here? And then things like running projects in Remote Containers that's been a game-changer with a dev container that you can also use with Codespaces. Once I switched over, there was no going back.

vim with ultimate vimrc (nerd-tree, lightline, etc)