Diagnostic picker doesn't show diagnostics if the filepath for the current file contains a '+' #7321
Unanswered
JuliusBrueggemann
asked this question in
Troubleshooting
Replies: 1 comment 1 reply
-
I can reproduce this with clangd but not rust-analyzer. clangd percent-encodes the helix/helix-term/src/commands/lsp.rs Lines 514 to 520 in 18e07ad I believe we need to normalize the Urls in the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
If a filepath contains a '+' character, the diagnostic picker will not display diagnostics in that file. The workspace diagnostic picker is unaffected by this. Presumably, other "special" character might also affect the diagnostic picker, even though I did not test with any other characters.
Reproduction Steps
Create the file
main.cpp
with the following content in a directory calledc++
(like~/c++/main.cpp
). clangd will correctly issue a diagnostic for this error (that Helix correctly displays):However, when opening the diagnostic picker with Space + d, the diagnostic does not appear:
On the other hand, the workspace diagnostic picker (Space + D) does show the diagnostic:
If
main.cpp
is instead placed in a directory whose path does not contain "special" characters like '+', the diagnostic picker works as expected:Helix log
No response
Platform
Linux
Terminal Emulator
GNOME Terminal 3.48.1 using VTE 0.72.2 +BIDI +GNUTLS +ICU +SYSTEMD (This is the output from
gnome-terminal --version
)Helix Version
helix 23.05 (7f5940b)
Beta Was this translation helpful? Give feedback.
All reactions