-
Notifications
You must be signed in to change notification settings - Fork 349
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
commit fa3911e changes how base16_gruvbox_dark_hard is loaded #250
Comments
happy-dude
changed the title
commit fa3911ebbdf80a88dcab7c948de33865c8b161ed changes how base16_gruvbox_dark_hard is loaded
commit fa3911e changes how base16_gruvbox_dark_hard is loaded
Apr 15, 2021
You might need to dig out further the differences, if it isn't fixed yet.
… Am 15.04.2021 um 19:02 schrieb Stanley Chan ***@***.***>:
I don't think the it quite fixed yet; can we reopen and investigate further?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I gave a shot at fixing it re: https://github.com/vim-airline/vim-airline-themes/pull/251/files Feel free to make suggestions/edits! |
chrisbra
added a commit
that referenced
this issue
Apr 16, 2021
Fix #250: Move color palette definitions in if-block for old base16_gruvbox_dark_hard
taigrr
pushed a commit
to taigrr/vim-airline-themes
that referenced
this issue
Sep 23, 2021
Set let g:airline_base16_gruvbox_dark_hard_old = 1 to allow the old base16_gruvbox_dark_hard style again. closes vim-airline#250
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey team, just started up neo/vim and realized that the airline theme was loaded differently.
Checked to see what the cause may be and found that commit fa3911e was merged in.
Unfortunately I'm not too knowledgeable about vim-theming, but I hope the following info + screenshots can help.
environment
if you are using terminal:
if you are using Neovim:
actual behavior
expected behavior
screen shot (if possible)
Please see above
The text was updated successfully, but these errors were encountered: