-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Airline theme breaks with transparent vim windows. #108
Comments
I found a work around for now, by changing the background using a vim autocmd, the change only takes effect after everything loads.
Does this perfectly. |
@ry-dgel I experienced similar problem and your solution works well, thanks 🎉 |
I was having this issue either with @ry-dgel autocmd Solution and without. So for me the solution was to define a different color for the background, like so: |
I am having the same issue when enabling transparency. The |
@normen Do you by any chance use the terminal for fzf only ? That was my case and for that I added an option to fzf.vim plugin to prevent it from using the terminal when available |
No, I am using a zsh with only a few options. I moved from airline to lightline and that seemed to fix the issue, plus some others 😄 |
I'm using Urxvt with real transparency and Compton as a compositor. In order to get a transparent background with nvim I set,
:hi Normal ctermbg=none
in init.vim.This causes a bunch of red to take over in vim-airline, as it gets the colors from the theme after the previous change is made. Without changing my init.vim, if I create a new window and then pass the previous statement as a command, everything works fine, as vim-airline has already read the right colors.
Before.
![2016-03-05-221500_931x43_scrot](https://cloud.githubusercontent.com/assets/14968322/13552075/ce89ffc2-e31f-11e5-8e4a-4d8507ee7af0.png)
After. (Statement in config.)
![2016-03-05-221433_923x40_scrot](https://cloud.githubusercontent.com/assets/14968322/13552076/ce8a0a30-e31f-11e5-9d47-0c350e40cae2.png)
How it should look. (Statement passed as command in existing window.)
![2016-03-05-221518_925x41_scrot](https://cloud.githubusercontent.com/assets/14968322/13552074/ce89980c-e31f-11e5-8840-7737e2ff48ee.png)
The text was updated successfully, but these errors were encountered: