Skip to content

Rich status bar support #9909

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

Closed
lnicola opened this issue Aug 15, 2021 · 2 comments · Fixed by #14313
Closed

Rich status bar support #9909

lnicola opened this issue Aug 15, 2021 · 2 comments · Fixed by #14313
Labels
A-lsp LSP conformance issues and missing features A-vscode vscode plugin issues C-feature Category: feature request S-actionable Someone could pick this issue up and work on it right now

Comments

@lnicola
Copy link
Member

lnicola commented Aug 15, 2021

See https://code.visualstudio.com/updates/v1_59#_rich-status-bar-hover.

We could have actions for status, memory usage, maybe even cancelling a running cargo check (an often-requested feature).

@lnicola lnicola added A-vscode vscode plugin issues S-actionable Someone could pick this issue up and work on it right now labels Aug 15, 2021
@lnicola lnicola added C-feature Category: feature request A-lsp LSP conformance issues and missing features labels Sep 13, 2021
@Milo123459
Copy link
Contributor

Hey 👋
I'd be happy to take this up. Here are some ideas I've had to display:
Display an X button next to cargo check: X cargo check, and that cancels it.
Show memory usage, and a toggle (which I believe has been added to rust-analyzer) to only show errors, not warnings.
If the last one hasn't been implemented, I'd be fine to implement that one as well.

@Zingam
Copy link

Zingam commented Dec 28, 2021

How about run, debug, etc. stuff?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-lsp LSP conformance issues and missing features A-vscode vscode plugin issues C-feature Category: feature request S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants