Steven Arcangeli

I'm trying to think of some way that this could be done without either me re-implementing everything in the Neotest summary window or vice-versa. I get the appeal of having...

Thanks for weighing in @rcarriga! @fnune what are your thoughts on that approach? It's more viable from a maintenance perspective, but the downside would be that there's potential for mismatch...

You're right, there aren't currently hooks for rendering custom content inline with the symbols. There _are_ currently sufficient APIs for performing actions, but you'd have to hook a lot of...

@fnune I'll give you a couple pointers for something quick and dirty. Note that these do not use public API methods, so expect that it may change in the future...

Yeah, that commit is probably where this changed. The trouble is there are some people that expect the floating window to auto-close, and some people that want it to remain...

I found two bugs. One of them was easy to fix, the other one I have filed upstream https://github.com/neovim/neovim/issues/27121

This appears to be fixed upstream now. Can you try it again on the most recent nightly?

When you say the symbols might be stale, what problem does this manifest as? Like if you've recently added a symbol it may not be present? Or there won't be...

Hmmm...this sounds like it might be related to the specific LSP server. Does this happen with other LSP servers? Another thing you can try is setting the config value `lsp.diagnostics_trigger_update...

If `lsp.diagnostics_trigger_update = false` fixes the problem, then it's probably just an issue with our interaction with the LSP diagnostics as a trigger to re-fetch symbols. I'll mark this issue...