Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

render diagnostic hides square brackets #280

Closed
Amleto opened this issue Mar 9, 2024 · 4 comments · Fixed by #281
Closed

render diagnostic hides square brackets #280

Amleto opened this issue Mar 9, 2024 · 4 comments · Fixed by #281
Labels
bug Something isn't working

Comments

@Amleto
Copy link

Amleto commented Mar 9, 2024

Neovim version (nvim -v)

v0.10.0-dev-2051+gee3d4f6b9

Operating system/version

win11 + wsl

Output of :checkhealth rustaceanvim

rustaceanvim: require("rustaceanvim.health").check()

Checking for Lua dependencies ~
- WARNING dap not installed. Needed for debugging features [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap)

Checking external dependencies ~
- OK rust-analyzer: found rust-analyzer 1.73.0-nightly (eb088b8 2023-08-05)
- OK Cargo: found cargo 1.73.0-nightly (d78bbf4bd 2023-08-03)
- OK rustc: found rustc 1.73.0-nightly (eb088b8b9 2023-08-05)

Checking config ~
- OK No errors found in config.

Checking for conflicting plugins ~
- OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- OK tree-sitter parser for Rust detected.

How to reproduce the issue

make a compiler error that contains square brackets, e.g. something involving an array.

Sorry, I will update later - same for the config.

This bug looks similar to #200, in that treesitter is probably hiding the brackets, but I suspect this to be a rustacean issue if the filetype should not actually be set to markdown?

Expected behaviour

render diagnostic looks like the compiler output

Actual behaviour

The square brackets are gone (hidden). They reappear when focusing into the window setting the cursor on the same line as a 'bad render'.

The minimal config used to reproduce this issue.

.
again, apologies - will endeavour to update tomorrow
@Amleto Amleto added the bug Something isn't working label Mar 9, 2024
@mrcjkb
Copy link
Owner

mrcjkb commented Mar 9, 2024

Hey 👋

thanks for reporting!
A fix is in the pipeline 😄

@Amleto
Copy link
Author

Amleto commented Mar 9, 2024

Oh sweet! Thanks for looking into it even with the poor report 🙏🏻

I really like the render diag feature!

@Amleto
Copy link
Author

Amleto commented Mar 10, 2024

@mrcjkb btw, I know how to 'enter' the hover window with 2x hover. The same thing doesn't work with render diagnostic - how does one enter the render diagnostic float? (or scroll it when its not active)?

@mrcjkb
Copy link
Owner

mrcjkb commented Mar 10, 2024

@mrcjkb btw, I know how to 'enter' the hover window with 2x hover. The same thing doesn't work with render diagnostic - how does one enter the render diagnostic float? (or scroll it when its not active)?

I usually use <C-w> followed by w (cycle windows).
For scrolling, I'd probably have to implement something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants