7ade7d8e45
Closes https://github.com/zed-industries/zed/issues/14334, allowing users to set environment variables for a language server binary like: ```json "lsp": { "rust-analyzer": { "binary": { "path": "/Users/dbarsky/.cargo/bin/rust-analyzer", "env": { "RA_PROFILE": "*>100" } }, } } ``` The newly introduced environment variables are merged with the shell environment. Perhaps more controversially, I've _also_ removed the trimming/`stderr:`-prefixing of language server logs. This because rust-analyzer has some nice, tree-shaped profiling built-in, and it prevents us from printing profiles like this: <details> <img width="1147" alt="Screenshot 2025-03-20 at 12 09 14 PM" src="https://github.com/user-attachments/assets/b7066651-6394-492b-b745-906c66d3c7b2" /> </details> Release Notes: - Added the ability to set a language server's environment variables. - Removed the `stderr`-prefix of a language server's stderr logs.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.