BUG: Black/White background color on interactive windows since neovim v0.10 #1480
Comments
Nukesor
changed the title
|
I played around a bit more and found out that the issue doesn't happen on the habamax: vim: What's confusing though is that the default neovim colorscheme has this problem as well as the other three colorschemes I tested. So I assume this is an issue introduced with the new colorscheme? default: |
|
I am also experiencing a similar issue. I observe the black background on the status lines of inactive windows and inside the Lazy UI. I'm not certain if it was the cause but I started noticing the behavior after installing lualine and setting cmdheight=0 but reverting these actions didn't fix it. |
|
Same thing here. The Lazy UI is affected as well, including the top bar. What's interesting is that the Lazy UI uses and sets the |
Nukesor
changed the title
|
Just popping in here to confirm that I can recreate your issue with the provided config. What's interesting is if you add literally any valid value for local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
vim.fn.system({
"git",
"clone",
"--filter=blob:none",
"https://github.com/folke/lazy.nvim.git",
"--branch=stable", -- latest stable release
lazypath,
})
end
vim.opt.rtp:prepend(lazypath)
require("lazy").setup({
{
"nvim-neo-tree/neo-tree.nvim",
dependencies = {
"nvim-lua/plenary.nvim",
"MunifTanjim/nui.nvim",
},
branch = "main",
config = {
popup_border_style = "single",
}
},
})
vim.cmd(":Neotree source=filesystem")Valid values for border: Style of (optional) window border. This can either
be a string or an array. The string values are
• "none": No border (default).
• "single": A single line box.
• "double": A double line box.
• "rounded": Like "single", but with rounded corners
("╭" etc.).
• "solid": Adds padding by a single whitespace cell.
• "shadow": A drop shadow effect by blending with the
background.
• If it is an array, it should have a length of eight or
any divisor of eight. The array will specify the eight
chars building up the border in a clockwise fashion
starting with the top-left corner. As an example, the
double box style could be specified as:
[ "╔", "═" ,"╗", "║", "╝", "═", "╚", "║" ].
If the number of chars are less than eight, they will be
repeated. Thus an ASCII border could be specified as
[ "/", "-", \"\\\\\", "|" ],
or all chars the same as
[ "x" ].
An empty string can be used to turn off a specific border,
for instance,
[ "", "", "", ">", "", "", "", "<" ]
will only make vertical borders but not horizontal ones.
By default, `FloatBorder` highlight is used, which links
to `WinSeparator` when not defined. It could also be
specified by character:
[ ["+", "MyCorner"], ["x", "MyBorder"] ].Not really sure what is going on but this workaround seems to work for me. Without setting With setting IIRC Neo-tree uses nui for the popup handling, might be a nui regression? |
|
Sorry, I realized my issue was unrelated (I don't use neo-tree). If it helps the behavior I observed was due to enabling transparent floating windows with my theme (kanagawa-dragon) but I accidentally copied over an override for the LazyNormal highlight group which caused the Lazy floating window to have a black background. |
|
I'm at this point very sure that this has to do with old color schemes. The ported lua variant of gruvbox works just fine, so I'll guess I'll close this for now. |
Did you check docs and existing issues?
Neovim Version (nvim -v)
0.10.0-2
Operating System / Version
ArchLinux 6.8.9-arch1-2Describe the Bug
All hover windows (rename, move, etc) have a pure black/white background, based on the colorscheme's style(dark/light). This started to occur with the update to neovim 0.10. I also tested several color schemes, including neovim's default scheme and it appears on all of them.
I experience the same behavior for hover windows of
lspsagaand lazy's hover window.skimhover windows however seem to work just fine.Things I tried
xtermandalacritty) , but it appears on both terminals.settermguicolorsis activated, the behavior appears.Workaround
Setting
set :notermguicolorsfixes the problem! It just looks bad.Similar issues
I stumbled upon this neovim issue, but it seems to be a different problem, even though it sound suspiciously similar. Their minimal config works perfectly fine on my system and the transparent windows is displayed correctly.
Screenshots, Traceback
Trace log of the event:
Steps to Reproduce
mon neo-tree to openmovemenu.Expected Behavior
The background shouldn't switch to black/white.
Your Configuration
The text was updated successfully, but these errors were encountered: