Closed
Conversation
Member
|
The syntax is fine, it's supposed to be monospace, but the dialog probably doesn't accept Markdown. |
Member
|
Yes the bug is likely on the typescript side not telling vscode its markdown |
Member
|
Yes the issue is here rust-analyzer/editors/code/src/ctx.ts Line 449 in 8dd53a3 This ought to be appendMarkdown
|
bors
added a commit
that referenced
this pull request
Oct 22, 2024
Fix status bar messagen not being marked markdown Closes #18323
bors
added a commit
that referenced
this pull request
Oct 22, 2024
Fix status bar message not being marked markdown Closes #18323
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Oct 29, 2024
…Veykril Fix status bar message not being marked markdown Closes rust-lang/rust-analyzer#18323
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There's a small bug in the Markdown syntax for the below dialog:
Removing the backticks should fix this.