YouCompleteMe | A code-completion engine for Vim | Plugin library

for go I preferred vim go this is the good plugging for go.

Alright after some trying I found the following: it looks like I made a blunder. After putting let g:ycm_global_ycm_extra_conf = '~/Documents/code/.ycm_extra_config.py' in my .vimrc it was fixed.

All it needed was the full path, including the filename.

The reason this is happening is because the version of the clang compiler that I was using, which is installed via Xcode, is out of date. I am on Mojave, and I cannot update my Xcode (thereby upgrading my clang) until I upgrade to a newer OS. Simply put, for macs, Mojave is too old to install the current branch of YCM via the normal installation path. I have spoken to the devs and this may be noted in the README in the near future.

It can be included in multiple compilation units. If you mark the definition inline it should be happy.

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!):

Seems like it's related to the scoping. When I move push/pop #pragmas outside of a variable's block GCC behaves just well. For example:

This answer is for everyone, who wants to install powerline only in vim in the windows terminal (using wsl Ubuntu 20.04). It took me quite some time.

The reason why I had this issue was that glyphs where missing in the windows terminal font. I tried to install the powerline fonts according to the documentation(https://powerline.readthedocs.io/en/latest/installation/linux.html#fontconfig) as @romainl suggested but that didn't work. Furthermore I tried to install all powerline fonts from the github(https://github.com/powerline/fonts), I ran both the installation scripts. The one for windows in the powershell console according to this blog() and the one for Linux on the Ubuntu WSL Machine according to the documentation. Didn't work either. Then I stumbled upon a blog post of Microsoft(https://docs.microsoft.com/en-us/windows/terminal/tutorials/powerline-setup), where the person installed a theming framework oh-my-posh. However, I neither wanted to install a theming framework nor a special version of git. Furthermore I only wanted to install powerline in vim not in my whole console. This was the moment when I asked myself: did I miss something? And indeed I did catch a little detail. The answer was to install a the Cascadia Mono PL font (https://github.com/microsoft/cascadia-code/releases) which includes the missing glyphs. Just download the zip and double click on the font. Furthermore I had to set the fontface in the setting.json of the windows terminal (which can open with pressing (CTRL + ,) in the terminal). Your settings should look something like this:

In this case the snippet is not expanded because it is preceded by $ without any whitespace in between. Try adding i to the first line of the snippet:

Vim uses the Python interpreters it was compiled with. No setting will affect it. If you can't find a Vim binary with the desired Python support, the only way to make Vim use Python3.6 is to compile it with Python3.6 yourself. See --enable-python3interp, --with-python3-command and --with-python3-config-dir options to Vim's configure.