Vim VS nnn.vim

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

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

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.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

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 ...

So these days I just use https://github.com/mcchrish/nnn.vim

Yeah I'm not sure what the point is of such a minimal plugin when nnn.nvim and nnn.vim already exist which both do do that, and more.

file managers or project/directory viewer

nnn with nnn.vim because I'm lazy and I already use nnn on its own.

Created this plugin because I've switched from Ranger to xplr.nvim as my daily driver and wanted a cleaner interaction between the 2 programs. I like to sometimes use my file manager within neovim, and would prefer not to use shell to exchange data between them. Because xplr now uses LuaJit, pynvim/python isn't needed etc (like other msgpack plugins) It aims to support the "regular" features (opening files in nvim, switch cwd etc) like in rnvimr or nnn.vim

You can try nnn.vim, a vim-ish file picker as well as fast and full-featured file manager within vim.

You'll invoke it as a floating window. See nnn.vm for usage.