nvimdev / nvimdev/lspsaga.nvim

Winbar has a differenent bg color

Open
#1,409 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Lua
Stars
3.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

image
I didn't really figure out how to give it the same color as my neovim background, so that it doesnt look that annoying, thx for the plugin anyways...

Steps to reproduce

Use rose-pine theme with that config:
require("rose-pine").setup({
variant = "main", -- auto, main, moon, or dawn
dark_variant = "main", -- main, moon, or dawn
dim_inactive_windows = false,
extend_background_behind_borders = true,

enable = {
    terminal = true,
    legacy_highlights = true, -- Improve compatibility for previous versions of Neovim
    migrations = true, -- Handle deprecated options automatically
},
styles = { bold = true, italic = true,
    transparency = true,
},

--  groups = {
    --  border = "muted",
    --  link = "iris",
    --  panel = "surface",

    --  error = "love",
    --  hint = "iris",
    --  info = "foam",
    --  note = "pine",
    --  todo = "rose",
    --  warn = "gold",

    --  git_add = "foam",
    --  git_change = "rose",
    --  git_delete = "love",
    --  git_dirty = "rose",
    --  git_ignore = "muted",
    --  git_merge = "iris",
    --  git_rename = "pine",
    --  git_stage = "iris",
    --  git_text = "rose",
    --  git_untracked = "subtle",

    --  h1 = "iris",
    --  h2 = "foam",
    --  h3 = "rose",
    --  h4 = "gold",
    --  h5 = "pine",
    --  h6 = "foam",
--  },

highlight_groups = {
    --  -- Comment = { fg = "foam" },
    --  -- VertSplit = { fg = "muted", bg = "muted" },
    --  --  TelescopeBorder = { fg = "highlight_high", bg = "none" },
	--  --  TelescopeNormal = { bg = "none" },
	--  --  TelescopePromptNormal = { bg = "base" },
	--  --  TelescopeResultsNormal = { fg = "subtle", bg = "none" },
	--  --  TelescopeSelection = { fg = "text", bg = "base" },
	--  --  TelescopeSelectionCaret = { fg = "rose", bg = "rose" },
    Boolean = { fg = '#ffb8f1' },
    ["@function.builtin"] = { fg = "#772dbc" },
    --  --  ["@constant.builtin"] = { fg = "rose"},
    --  String = { fg = "#5ff5cf"},
    --  ["@property"] = { fg = "love", italic = italic },
    ["@variable"] = { fg = '#548a7a' },
    ["@function"] = { fg = 'love' },
	["@variable.member"] = { fg = '#548a7a'},
    --  ["@function.method"] = { fg = 'love' },
    Function = { fg = '' },
},

--  before_highlight = function(group, highlight, palette)
    --  -- Disable all undercurls
    --  if highlight.undercurl then
        --  highlight.undercurl = false
    --  end
    --  --
    --  -- Change palette colour
    --  if highlight.fg == palette.pine then
        --  highlight.fg = palette.pine
    --  end
--  end,

})
-- -- vim.api.nvim_set_hl(0, '@lsp.type.function', {})

vim.cmd("colorscheme rose-pine")
-- -- vim.cmd("colorscheme rose-pine-main")
-- -- vim.cmd("colorscheme rose-pine-moon")
-- -- vim.cmd("colorscheme rose-pine-dawn")
2) open packer.lua or whatever file you want and you should see this on top

Expected behavior

Same background as the neovim theme aka rose-pine

Neovim version (nvim -v)

0.9.5

lspsaga commit
Terminal name/version

kitty

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with Neovim 0.9.5, the rose-pine configuration shown, and kitty, then open packer.lua or another file to inspect the winbar background. Trace the winbar styling used by lspsaga and compare it with the rose-pine background; done means the winbar matches the Neovim theme without the contrasting color.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, neovim
Domain
design, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.