Closed jt4201 closed 10 months ago
Spent some time with the docs and found a switch that solves this.
vim.g.nightflyNormalFloat = true
The highlight group definitions which come directly from 'mini.pick' are there only as default values. This means that they are (hopefully) reasonable choices which should work with most color schemes. But not all.
Dealing with highlight groups which come from color scheme is suggested to be done by user. It is perfectly appropriate to have :colorscheme ...
call followed by some user adjustments. Like in this case followed by vim.api.nvim_set_hl(0, "MiniPickMatchCurrent", { standout = true })
. To work with any color scheme, these adjustments can be put in the autocommand for ColorScheme
event.
After bluz71/vim-nightfly-colors#61 there should be now better support for 'mini.pick'.
Contributing guidelines
Module(s)
mini.pick, mini.extra
Description
In
mini.pick
,MiniPickMatchCurrent
is linked toCursorLine
andMiniPickNormal
is linked toNormalFloat
In bluz/vim-nightfly-colors, both
CursorLine
andNormalFloat
setbg=dark_blue
. This makes the current line look the same as the background.There is already a limited Mini... highlights section in nightfly. I read the section about updating colorschemes, but since the Mini highlights already exist, some one may already "own" this.
My workaround is to set
MiniPickMatchCurrent
to{ standout = true }
Neovim version
0.9.5
Steps to reproduce
.config/nvim-test/init.lua
Expected behavior
you can see the current line with a highlight
Actual behavior
current line is not highlighted