Vim VS vundle

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

I'm confused. What install guide are you talking about to be specific (as in, please actually send a link)? The official repository is at https://github.com/VundleVim/Vundle.vim and it doesn't mention Python at all. From what I understand Vundle is not written in Python and should not have a dependency to it. If in doubt, consult official documentation rather than third-party tutorials and guides which could be wrong and/or including extra steps that are not necessary.

Vundle https://github.com/VundleVim/Vundle.vim

For example, a link to Git for Windows on Vundle's wiki was replaced with a link to malware:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_compare/3aeb22ac39229af4312f2be1052ead184dd5b54d...aa3d293dd18ae1cb4f049c43b73b951651515863

In fact, all five recent edits, made by three different accounts, were malicious:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_history

I recommend restricting editing in your GitHub wikis to collaborators only.

## Vundle Install Script function install-vundle() { git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim; sudo gem install vundle-cli; if ! grep -Fxq 'set rtp+=~/.vim/bundle/Vundle.vim' ~/.vimrc then echo "\nset nocompatible\nfiletype off\nset rtp+=~/.vim/bundle/Vundle.vim\ncall vundle#begin()\n\nPlugin 'VundleVim/Vundle.vim'\n\ncall vundle#end()\nfiletype plugin indent on" >> ~/.vimrc; fi }

A typo. I meant vundle. VimBundle