Kirill Bulatov

Thank you for coming up with the test nonetheless! It does look good logically (as the change is too) and seems to work for me on the branch, at least....

Passing by, but would like to notice that I would prefer splitting the debounce out of this PR: mixing different UI and functional changes seem dangerous, esp. given that either...

Thank you for the debounce removal: if you plan to submit another PR with that, I'd propose to make it configurable, since whatever forced value we pick, there will be...

Could you recheck this on Zed 0.132 (or above, if happens later) and, if the issue persists, provide more details — which language extensions do and do not have it...

Thanks, indeed files with languages that do not have tasks, have blank `ZED_FILE` on Stable and Preview improves the general logic, filtering such tasks away entirely. I'll work on a...

https://github.com/zed-industries/zed/pull/10764

Can we have some kind of a setting for this? (enabled/disabled at least). My main issue with VSCode's impl is that they hardcode the debounce and never allow it to...

I'll add a patch for that soon-ish then, seems rather minor and we should not suddenly change the 0 debounce inlay hint updates before Wednesday anyway, due to the same...

* we do not have any LSP-level configs that start with `source`: https://github.com/zed-industries/zed/blob/e01a6066164fb27b498f6d2d070b420fb8c66620/crates/project/src/project_settings.rs#L63-L68 So I wonder if that value has to be passed in the `initialization_options`? ```json "lsp": { "rust-analyzer":...

It would break everybody's existing configs for sure, so if we're planning to break it, I would suggest to do something more human-readable as VSCode has it: `rust-analyzer.rustc.source`. Maybe we...