You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thank you for forking rust-tools, your approach to plugins is really nice, hopefully this fork will live long!
I found the repo following the bug where multiple instances of RA were spawned. Thanks for fixing that so fast!
I found a "bug" in the Rust HoverActions, previously on rust-tools, the syntax highlighting with themes and TreeSitter (correct me if I'm wrong) was used. Now when I hover functions the text seems plain and it's not parsed by the theme which uses TS.
Would be nice to maintain that as it's clearer when reading rust-docs.
Let me know if this is intended and there should be flagged as enhancement instead of bug.
Expected behaviour
Actual behaviour
The minimal config used to reproduce this issue.
Open a rust project and hover a documented function such as tracing_subscriber
The text was updated successfully, but these errors were encountered:
I guess if you set that to false, you'll have the old behaviour back.
But I did configure hover actions to use tree-sitter highlighting (they didn't before, iirc).
I do this by setting vim.bo[bufnr].ft = 'markdown'. But I've only tested this with Neovim nightly. Maybe it doesn't work in Neovim 0.9.4?
Neovim version (nvim -v)
v0.9.4
Operating system/version
Archlinux
Output of
:checkhealth ferris
Everything prints OK
How to reproduce the issue
First of all thank you for forking rust-tools, your approach to plugins is really nice, hopefully this fork will live long!
I found the repo following the bug where multiple instances of RA were spawned. Thanks for fixing that so fast!
I found a "bug" in the Rust HoverActions, previously on rust-tools, the syntax highlighting with themes and TreeSitter (correct me if I'm wrong) was used. Now when I hover functions the text seems plain and it's not parsed by the theme which uses TS.
Would be nice to maintain that as it's clearer when reading rust-docs.
Let me know if this is intended and there should be flagged as enhancement instead of bug.
Expected behaviour
Actual behaviour
The minimal config used to reproduce this issue.
Open a rust project and hover a documented function such as tracing_subscriber
The text was updated successfully, but these errors were encountered: