vim-mark VS Vim

Do you know vim-mark: https://github.com/inkarkat/vim-mark.

Although, now I use vim-mark instead.

https://github.com/inkarkat/vim-mark may be of interest (the README also has a 'related works' section).

You can open result in current window. You can select multiple results into quickfix (and then do e.g. :cfdo...). You can go through results and you have preview with the context of the result line. When you mark more strings by e.g. https://github.com/inkarkat/vim-mark you have fast visual overview of more complex information (you search for an expression but other highlighted expressions in context allows you to decide faster if the result is relevant).

I tried out vim-mark recently but unfortunately it doesn't seem to work with Neovim. Does anyone know of an alternative that has similar functionality? I'm looking for something that can highlight several different searches/selections in different colors.

inkarkat/vim-mark I use this plugin SO much, especially when attempting to grok old, hard-to-follow codebases or massive xml config files that I frequently inherit.

Check out inkarkat/vim-mark or Pocco81/HighStr.nvim.

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