Open rperryng opened 1 month ago
can you give the output of :echom &ft
before the hydra is opened, and then again after things have broken?
Yes sure thing, here's a screencap to demonstrate:
:echo &ft
(prints lua
):echo &ft
(still prints lua
)echo &ft
(which prints nothing, also no syntax highlighting) and :LspInfo
/:LspLog
Can you send the hydra you're using, I can't reproduce this with my windows hydra, or my options hydra, both of which create floating hints.
Yep, definitely. Actually, I was able to reproduce the syntax highlighting issue without having any other plugins installed... here's the entire config:
❯ tree ~/.config/nvim-hydra7
/Users/rperryng/.config/nvim-hydra7
├── init.lua
└── lazy-lock.json
I'm unable to reproduce with the latest commit from main, is there anything keeping you from updating the plugin?
https://github.com/user-attachments/assets/de102b46-19dc-4004-a0c6-a13e0d6a1ba3
Aghh sorry, I didn't realize I was on an older version... i assumed that when I changed from using the original repo to the fork that lazy would pull the latest version but I guess as long as the commit sha in my lazy-lock.json
was still valid that it wouldn't try to update it... really sorry about that.
It does seem the latest version works fine for the minimal example I gave but I still see the issues with my main configuration with all other plugins, I'll see if I can produce another minimal example with the latest version of nvimtools/hydra.nvim
.
Hey there, I was hoping to bring some attention to an existing issue in the original repo:
It seems that activating a hydra with
config.hint.type = 'window'
seems to break treesitter integration somehow.Setting any other kind of
config.hint.type
window luckily avoids the problem.I can't seem to find any related error logs (via
:messages
or:LspInfo
/:LspLog
). The behaviour I see is::LspInfo
shows the old language server still running, but does not attach to the new bufferI apologize for the lack of details, happy to provide a minimal reproducible example if needed. I will also try to dig through the code when I have some more time to try and understand the root cause. Thanks.