Replies: 1 comment 6 replies
-
|
Do you use |
Beta Was this translation helpful? Give feedback.
-
|
The vim configuration for CoC plugin (apart of the JSON file) looks like this: https://gist.github.com/mareq/25fa15abbde7d1114f00c25b677e7560 I guess the only relevant part is the one that makes it display the error in pop-ups instead of echoing them (it will be one of the lines below the line 62 if I remember correctly). |
Beta Was this translation helpful? Give feedback.
-
|
Also (only somewhat related to the issue at hand), I do not seem to be able to pass that |
Beta Was this translation helpful? Give feedback.
-
|
Have no idea about this. Can you reproduce this error with VSCode + rust-analyzer extension? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I do not have VSCode - never had... 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
To close the loop: the issue is being solved on the other side: |
Beta Was this translation helpful? Give feedback.
-
The
rust-analyzerreports and error about failingcargo check(there is intentionally introduced error by commenting out one of theuseclauses, so there is an undefined symbol referred to in the code). I have written up detailed description of the error in therust-analyzerrepository.The problem is, that this results in three identical floating windows popping up (or alternatively, the same error message consisting of many lines is echoed three times over, requiring hitting Enter to continue).
Is this works-as-designed, or is there some less intrusive possibility of reporting this kind of error? I guess the error needs to be reported somehow and it is quite possible that the actual problem is on the
rust-analyzerside? Still, would there be a way to suppress the error, or at least not reporting it three times over?Beta Was this translation helpful? Give feedback.
All reactions