vim-colors | Modern rewrite of Vim 's default colorschemes | Plugin 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.

I recently had this problem myself. When comparing your config files to mine, I have a few more lines than you.

tmux.conf:

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:

This will happen when you have Vim running with 'termguicolors' on. (You can confirm it and see where it's being enabled with :verb set tgc?.) Same as when running in a GUI (not the terminal), it will tell Vim to use 24-bit colors, and use the color scheme full RGB color specifications, rather than use the terminal color palette.

In that situations, Vim's colors get completely detached from those of the terminal where Vim is running, so Vim's built-in terminal no longer has access to the actual terminal colors.

You can set specific colors to use in Vim's built-in terminal with the g:terminal_ansi_colors variable (see :help g:terminal_ansi_colors for details.)

Alternatively, disabling 'termguicolors' should work as well. Assuming the Vim color scheme has been built in a way that will use the terminal color scheme to reproduce the same colors, it might not have other side effects in how Vim colors otherwise look.

The Pydiction plugin has not been maintained since 2014. YouCompleteMe, when configured correctly, should be able to do everything that Pydiction is able to do, and is still getting regular commits. You might consider just not using Pydiction.

Additionally, it's not usually a good idea to copy someones .vimrc wholesale, simply for reasons like this. Not saying that you can't, but if you do, you should take the time to read through the help documentation to make sure you understand what everything does.

However, if you really want to use Pydiction, a solution follows:

The plugin vim-scripts/Pydiction doesn't set g:pydiction_location by default. Since you're using Vundle with the default location, the included complete-dict should be located at ~/.vim/bundle/Pydiction/complete-dict. You'll need to set g:pydiction_location:

The listchars feature might have been enabled. Try disabling it with :set nolist

The mappings that include h as a prefix will cause this interference. Vim will wait for a timeout or additional keypress before executing your h mapping, since it wants to check whether you meant to press one of the longer mappings...

The easiest way to fix this is set alternate mappings for the vim-gitgutter commands. If you set up different mappings for those in your vimrc, vim-gitgutter itself will not create its mappings which are causing the interference.

The vim-gitgutter README suggests using g as an alternative prefix for these:

To set your own mappings for these, for example if you prefer g-based maps:

I didn't work for me either, I didn't spend too much time on researching why it wouldn't work, and turn to this one: https://github.com/lifepillar/vim-solarized8

And it works for me, try if it's working for you :)

BTW, be aware it does fall back to an approximate palette based theme if your terminal is not supporting true colors, I'm using windows terminal and it works fine, you actually don't have to put "set termguicolors" in your .vimrc. Hope it helps

This is a feature of vim-latexsuite.

The <++> (with an optional comment between the two +) is a placeholder, which can be jumped to (without leaving insert mode) via . So you can type in between ( and ) whatever you like, then move to after the closing parenthesis via , without leaving insert mode.

This feature can be disabled by setting g:Imap_UsePlaceHolders to 0. (Documentation) Personally, though, I can only recommend this little bit, in LaTeX as well as elsewhere -- it can be mighty useful, especially in combination with macros.