Closed neuromaancer closed 8 months ago
Don't think this is an issue of the plugin as many of us overwrite highlight groups.
What if you remove config = true
? As per Lazy.nvim: "To use the default implementation without opts set config to true."
Oh,I didn't put 'config=true'. It still didn't work for me, I am wondering if the hanky.nvim affect the highlight group.
I suspect that it's overwriting the highlight group.
My approach would be: Disable hanky, run :hi IncSearch
observe the outputs, re-enable hanky, run :hi IncSearch
observe the outputs and see if it is overwriting.
You are right, when I disabled yanky.nvim
it works.
I suspect the author has probably enabled force = true
in [nvim_set_hl](https://neovim.io/doc/user/api.html#nvim_set_hl()). Raise thie issue on their repo
Okay, I figured it out, when I yanked, actually I used yanky.nvim
, it used Search
highlight group not IncSearch
. Problem solved.
Your
minimal.lua
configError messages
No response
Describe the bug
I want to change the highlight of on_yank, but it didn't work. Use LazyVim. so the autocmd is like:
no variables in
on_yank
so the defaultIncSearch
highlight group is used. I changed theIncSearch
as indicated before, but no effect taken.Reproduce the bug
No response
Final checks
minimal.lua
config file above and still get the issue:checkhealth treesitter