-
Notifications
You must be signed in to change notification settings - Fork 254
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
Is it able to change the bg color of the which-key and floating windows? #430
Comments
You mean like this?
It indeed changes the bg of the which-key, but is it the same as the theme (I disable the theme when using vim/nvim in terminal, so the theme here is the theme of the terminal), check the screenshot, I cannot distinguish the text in the buffer and the text in which-key popup window. And the bg color of the floating window for fzf is still the same, check the screenshots. I tried other configs in ~/.spacevim, none of them works, it seems it is fixed, either the same of the theme or the ugly color in the screenshot. I want the bg of color for both which-key and floating window of fzf to be like #395 (comment) ,just slightly different from the theme. |
Your problem is mostly that you chose a wrong theme or you did something wrong in your hi link WhichKeyFloating Search Also search the vim help |
I found the problem:
Once I comment this part out, the bg color of which-key and floatwindow of fzf is quite normal. And
only affects for the bg color of which-key window, not for the bg color of floatwindow of fzf. I have to redefine
|
Before you continue, ensure you have read the README and wiki carefully. Note that low quality issue feedback might be closed directly.
Environment
Please complete these steps and check these boxes (by putting an
x
insidethe brackets) before filing your issue:
Put the contents of
:version
below:Put the contents of
:SpaceInfo
below:Problem Description
Currently when I'm using the feature of which-key or fzf, the background color of popup window is very ugly, is it able to change it?
The text was updated successfully, but these errors were encountered: