neovim | Go package for writing Neovim plugins | Code Editor library

If you just want to run a file quickly without any preparations, I'd recommend quickrun.vim. It has some preconfigured run-configurations so you just need to run :Quickrun to execute your current file and you can also customize it according to your needs.

If you want to have different running options (if it's that what you mean), than you could use the builtin :make command or this plugin: asynctasks.vim. This plugin gives you the ability to create "profiles" to switch between different execution "styles".

I've only tried QuickRun yet, so here's a little demonstration how it looks like (opened a bash file and python file):

You could also give asyncrun a try, which runs your executions (as the name says) asynchrony.

1. Install Git for Windows if you haven't already installed it.

2. Add the following line to your init.vim file.

   let $PATH = "C:\Program\ Files\Git\usr\bin;" . $PATH

3. Save and Reload NeoVim.

I'm not knowledgeable enough about XML to determine whether it's expected behavior nor can do proper tests, so I don't know if my solution is the best.

But if you suspect it to be a bug, then the best action would be to report¹ it on the official GitHub repository of XML runtime files: chrisbra/vim-xml-runtime.

I managed to get your expected results by applying this patch²:

To vim I am still curious about such solution, but in my zsh I have this function:

Try deleting the node_modules folder and then run the npm install command in your project's root folder.

The package neovim of your package manager provided the commands nvim (and possibly vim as well).

After removing the package via sudo apt remove neovim, those commands will be gone. Just by downloading a new version (outside the comfort of your package manager), you won't get a "command" installed. If you want to keep using this downloaded version, the easiest way to do so IMO would be to:

 1. Move or symlink the new executable to some new folder like ~/bin:

if isrunning were "true" you would enter the if branch, but that is obviously not the case.

echo adds a trailing newline so isrunning is more likely to be "true\n" which of course is unequal to "true".

Use echo -n to suppress the trailing new line or check vs the correct value or use string.find or string.match instead of the ==

From the bash manual:

echo echo [-neE] [arg …] Output the args, separated by spaces, terminated with a newline. The return status is 0 unless a write error occurs. If -n is specified, the trailing newline is suppressed...

Neovim delegates clipboard access to external application. As you don't have any it cannot work. This is clearly written to you in the picture above.

Windows clip is not supported, because it cannot read from clipboard; xclip won't work, because it needs X-server to work (isn't it obvious from its name?) and so on.

Normally Neovim makes use of win32yank to access Windows clipboard. So try to download it and put somewhere on WSL path.

Welcome to Vim!

I think most new vim users have been there. I certainly have! I wanted a 'vim as python IDE' and copied a whole bunch of stuff from every blog under the sun into my vimrc almost immediately after installing vim.

After some time spent fighting with all the settings, plugins and remaps I didn't understand, I decided to go through my vimrc, line by line and comment out anything I didn't understand (nearly all of it).

Then I used this more minimal vim for a while and whenever I decided I had a need for a certain feature, I checked the largely commented vimrc for anything that looked related, and/or googled for that particular feature only. Often you find that there is a built in method to do it with the core vim commands, and if not, then there are a lot of solutions for the problem (and often, you find that there is an even more powerful way that didn't occur to you - these are good days).

But the key is to not try and coerce vim into a huge IDE overnight! Let it happen gradually and things will make more sense, and you'll end up with a vimrc that you understand and therefore be in a position to add to it and tweak it.

The last thing I'll say is to recommend the following books:
'Learn VimScript the Hard Way' by Steve Losh
'Practical Vim' by Drew Neil, and his accompanying screencast series.
(Also there is The Primagean who does high quality youtube tutorials)

Having said all that, and acknowledging that an objective answer can't be given for your question, here is a minimal vimrc which has a few plugins and settings that do simple but very useful things (but do read up on them to understand how they work!):