StatusLine | Octoprint StatusLine Plugin | 3D Printing library

If you are using neovim there is an option called :h pumblend which can be used to change the transparency of the popup menu.

Are you sure gruvbox caused your vim to lose transparency? I am not sure if vim is able to change a terminal emulator's transparency. I or someone else might be able to advise you better if you post pictures of what has changed.

Maven Artifactory plugin 3.2.3 is recently released. This version includes a fix for this issue.

The root cause is a new field returned from Artifactory in the response of the upload REST API. The fix is to ignore new unknown fields instead of throwing the UnrecognizedPropertyException.

For more information see https://github.com/jfrog/build-info/pull/502.

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

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:

You must update Vim to v8.1 or later.

The closest I can get:

autocmd CmdlineEnter * redrawstatus

As always, autocommands belong in augroups. If you don't know what that means, it means that you want to copy and paste all of the following into your vimrc, not just that first line I gave:

1. Vim assigns the gnuplot filetype to *.gpi files out of the box.
2. Syntax highlighting for gnuplot is also built-in.

Therefore…

• Your two FiletType autocommands can't work as-is. They should match on gnuplot, not gp:

You could :help filter() the lines to get a list of lines containing TODO: