Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix NeoTree diagnostic signs background issue#410

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
Copilot wants to merge3 commits intomain
base:main
Choose a base branch
Loading
fromcopilot/fix-a06be7a3-5827-4764-a728-427ac1e56802

Conversation

Copy link
Contributor

CopilotAI commentedAug 19, 2025
edited
Loading

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 defaultSignColumn background (colors.bg1) instead of blending properly with NeoTree's own background, creating a visual inconsistency.

Image showing the issue

Root Cause

NeoTree uses a specific highlight groupNeoTreeSignColumn for its sign column area, but this group wasn't configured in gruvbox.nvim. Without this configuration, diagnostic signs fell back to using the defaultSignColumn styling, which has a background color that doesn't match NeoTree's appearance.

Solution

Added the missingNeoTreeSignColumn highlight group configuration:

NeoTreeSignColumn= {bg="NONE"}

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

  • lua/gruvbox.lua: AddedNeoTreeSignColumn = { bg = "NONE" } configuration
  • tests/gruvbox/gruvbox_spec.lua: Added test case to verify the fix works correctly

The 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 moreCopilot coding agent tips in the docs.

…onfigCo-authored-by: ellisonleao <178641+ellisonleao@users.noreply.github.com>
CopilotAI changed the title[WIP] Identify the issue on @ellisonleao/gruvbox.nvim/issues/405 and create a PR to fix itFix NeoTree diagnostic signs background issueAug 19, 2025
CopilotAI requested a review fromellisonleaoAugust 19, 2025 19:51
Copilot finished work on behalf ofellisonleaoAugust 19, 2025 19:51
@smathles
Copy link

Unfortunately this doesn't work. I don't knowwhy it doesn't, but I've already tried setting the value ofNeoTreeSignColumn to various values. Maybe there is a way to do it with this parameter, but this isn't it unfortunately and I haven't figured what works yet.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@ellisonleaoellisonleaoAwaiting requested review from ellisonleao

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[BUG] Diagnostic signs in neotree have wrong background

3 participants

@smathles@ellisonleao

[8]ページ先頭

©2009-2025 Movatter.jp