Kirill Bulatov

Nice find. Two notes: * It seems safer to have a prefix as a non-relative path. We have `installation_path` after installing node, where we put the cache, seems that we...

re: relative path My main idea was to use a more explicit path form to see it in the node logs somewhere, if only the node command fails: otherwise, the...

One possibility would be to use tasks and do something similar to https://github.com/zed-industries/zed/pull/10548/files#diff-555038673fd8f3dcee873862e12320197c756e5661ada52d90b94339c56f0266 does for bash: there's a way to spawn a bash task that runs the selection. Presumably, Haskell...

This is a relatively hard issue to tackle, if put in a generic form as "[any] items in `.gitignore` should still be searchable via file finder". The hardest part would...

One amazing capability rust-analyzer provides is a "secret" unresolved reference diagnostics. When VSCode is additionally configured with ``` "editor.semanticTokenColorCustomizations": { "enabled": true, "rules": { // All-themes colors "unresolvedReference": { "foreground":...

Note: at least in the code names, we seem to deal with the "family name" only: https://github.com/zed-industries/zed/blob/f7a2118b159ac98a4fda8f15974090781522b407/crates/gpui/src/platform/mac/text_system.rs#L52 While `Bold`, `Italic`, etc. are not really names and that's why we might...

I have nothing against providing these, we should do that. My take was supposed to mean "current Zed seems to have zero mechanisms to look up a font by the...

There are some attempts but look stale currently: https://github.com/zed-industries/zed/pull/6782

@luhc228 what has Rust project to do with Elixir LSP issues from 2023? Please share more details, and if it's indeed related to Rust, in another issue.

This looks doable, see https://github.com/zed-industries/zed/pull/2786 for the reference. One needs to create another `Editor::manipulate_lines` wrapper and another action for that + add a test into `editor_tests.rs`