Fix NeoTree diagnostic signs background issue#410
Closed
Conversation
…onfig Co-authored-by: ellisonleao <178641+ellisonleao@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Identify the issue on @ellisonleao/gruvbox.nvim/issues/405 and create a PR to fix it
Fix NeoTree diagnostic signs background issue
Aug 19, 2025
|
Unfortunately this doesn't work. I don't know why it doesn't, but I've already tried setting the value of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Diagnostic signs in NeoTree file explorer were displaying with an incorrect background color that didn't match the rest of the NeoTree interface. The signs inherited the default
SignColumnbackground (colors.bg1) instead of blending properly with NeoTree's own background, creating a visual inconsistency.Root Cause
NeoTree uses a specific highlight group
NeoTreeSignColumnfor its sign column area, but this group wasn't configured in gruvbox.nvim. Without this configuration, diagnostic signs fell back to using the defaultSignColumnstyling, which has a background color that doesn't match NeoTree's appearance.Solution
Added the missing
NeoTreeSignColumnhighlight group configuration:This makes the sign column background transparent, allowing NeoTree's own background styling to show through properly. The diagnostic signs now blend seamlessly with the rest of the NeoTree interface.
Changes
NeoTreeSignColumn = { bg = "NONE" }configurationThe change follows existing code patterns in the theme (similar to how
["@none"]is configured) and is minimal and surgical - addressing only the specific issue without affecting other functionality.Fixes #405
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.