rust-lang / rust-lang/rust-analyzer

Avoid using error background color in status bar unless absolutely necessary

Open
#13,281 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

C-enhancement
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

rust-analyzer version: 0.4.1217-standalone (5b49745d0 2022-09-20)

rustc version: It's not installed

The VS Code codebase just had some Rust code committed for the first time and I saw this after restarting this morning:

image

This is on my Windows machine where I have no desire to install Rust. I understand this status bar item is important to diagnose what's wrong with rust-analyzer, but some repos contain rs files where the developer doesn't need to touch or compile them ever. I suggest you show this status bar conditionally, only when a .rs file is open.

The alternative is for me to uninstall the extension which I'd rather not do if it's well behaving wrt activation. I also don't want to right click to hide the item as in case I need it to diagnose (I think that gets synced too).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the VS Code extension code that creates the rust-analyzer status bar item and trace when it is activated; the issue proposes showing it only while a .rs file is open. Done means repositories without an open Rust file no longer show the error-colored item, while opening a .rs file still exposes it for diagnostics.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, vscode
Domain
developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.