Today after updating the plugin to bb3dc1a9fa34c3577bca627b848625e94a93efe8 I noticed that require("hover").hover() yields a result for $current_line + 1 instead of $current_line:
Here is my lazy.nvim package def and config for hover.nvim:
...and I have a normal mode keymap for K which just calls require("hover").hover(). I can also reproduce the problem by running this without the keymap (e.g. :lua require("hover").hover()).
All of my other LSP mappings (definition, declaration, code-action, etc all work normally) are working fine.
Reverting to 24369e8595736077e30b3ca5fc233f44abeccb8b fixes the problem, so I suspect that there might be some unintentional breakage from these two recent commits
I'll try to writeup a minimal repro config when time permits. If there's anything else I can do to help troubleshoot in the meantime, lemme know!
Hiya :wave:
Today after updating the plugin to bb3dc1a9fa34c3577bca627b848625e94a93efe8 I noticed that
require("hover").hover()
yields a result for$current_line + 1
instead of$current_line
:Here is my lazy.nvim package def and config for
hover.nvim
:...and I have a normal mode keymap for
K
which just callsrequire("hover").hover()
. I can also reproduce the problem by running this without the keymap (e.g.:lua require("hover").hover()
).All of my other LSP mappings (definition, declaration, code-action, etc all work normally) are working fine.
Reverting to 24369e8595736077e30b3ca5fc233f44abeccb8b fixes the problem, so I suspect that there might be some unintentional breakage from these two recent commits
I'll try to writeup a minimal repro config when time permits. If there's anything else I can do to help troubleshoot in the meantime, lemme know!