akinsho / akinsho/bufferline.nvim
[Bug]: Cannot set transparency whatsoever. Defaults to terminal background color.
- Langage dominant
- Lua
- Étoiles
- 4.4k
- Forks
- 240
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### What happened?
I'm using nvim on windows with the terminal from microsoft store.
i've tried manually setting to none using cmdline `:lua nvim.api.nvim_set_hl(...)`
It seems to be defaulting to what I've configured on the terminal and I can't seem to get transparency whatsoever.
I've seen the [help issue asking how to set transparency](https://github.com/akinsho/bufferline.nvim/issues/1021) but there wasn't anything useful
I just want to fully see cute anime girls while I program, man. 😔
### What did you expect to happen?
Transparency
### Config
```
require('bufferline').setup({
options = {
custom_filter = function(buf_num, _)
return vim.bo[buf_num].buftype ~= "terminal"
end
},
highlights = {
fill = {
bg = 'none',
},
background = {
bg = 'none',
},
buffer_visible = {
bg = 'none',
},
buffer_selected = {
bg = 'none',
fg = '#16a5e4'
}
}
})
```
### Additional Information
...
### commit
655133c
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reproducing the configuration in the issue on Neovim for Windows, focusing on the `require('bufferline').setup` highlights entry point and comparing it with `nvim.api.nvim_set_hl(...)`. No file or test is named in the report; done means the listed bufferline highlight groups render with `bg = 'none'` instead of the terminal background, with regression coverage for the behavior.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- lua
- Domaine
- tooling
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 62/100