| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
It looks like VS Code server chooses a different location for `globalStorage`.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
5885: Make inlay hints colors more configurable r=matklad a=Veetaha
**[BREAKING CHANGE]**
Tackles https://github.com/rust-analyzer/rust-analyzer/issues/5337#issuecomment-680018601 and generally related to #5337.
Added `foreground/background` color configurations with optional more specific overrides `foreground.(type|parameter|chaining)Hints`.
One problem I see is that the config keys are long and don't fit into the on-hover hints in the `settings.json` file entirely...
<details>
<summary>Demo</summary>
![demo](https://user-images.githubusercontent.com/36276403/91238334-77fc3b00-e745-11ea-836b-2822015ece98.gif)
</details>
Co-authored-by: Veetaha <[email protected]>
|
| | |
|
|/
|
|
|
| |
There's a surprising lack of crates which are like env_logger, but
also allow writing to a file. Let's write our own then!
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
5473: Changes to rust-project.json r=matklad a=matklad
Co-authored-by: Aleksey Kladov <[email protected]>
|
| |
| |
| | |
Co-authored-by: Laurențiu Nicola <[email protected]>
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
5407: Mentioned problem matchers and running cargo-watch as a VS Code Task r=matklad a=Michael-F-Bryan
See https://github.com/rust-analyzer/rust-analyzer/issues/3596#issuecomment-658887055.
Co-authored-by: Michael-F-Bryan <[email protected]>
Co-authored-by: Michael Bryan <[email protected]>
|
| |
| |
| | |
Co-authored-by: Laurențiu Nicola <[email protected]>
|
| |
| |
| | |
Co-authored-by: Laurențiu Nicola <[email protected]>
|
| |
| |
| | |
Co-authored-by: Laurențiu Nicola <[email protected]>
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Co-authored-by: Laurențiu Nicola <[email protected]>
|
|
|
| |
GNOME Builder (Nightly) supports now rust-analyzer
|
| |
|
| |
|
| |
|
|
|