Agus Zubiaga
8561943095
At some point, rust-analyzer started including the snippet expression for some completions in the description field, but that can look like a bug: <img width="1570" height="578" alt="CleanShot 2025-11-27 at 20 39 49@2x" src="https://github.com/user-attachments/assets/5a87c9fe-c0a8-472f-8d83-3bc9e9e00bbc"></img> In these cases, we will now inline the tab stops as an ellipsis character: <img width="1544" height="428" alt="CleanShot 2025-12-01 at 10 01 18@2x" src="https://github.com/user-attachments/assets/4c550891-4545-47cd-a295-a5eb07e78e92"></img> You may also notice that we now syntax highlight the pattern closer to what it looks like after accepted. Alternatively, when the tab stop isn't just one position, it gets highlighted as a selection since that's what it would do when accepted: <img width="1558" height="314" alt="CleanShot 2025-12-01 at 10 04 37@2x" src="https://github.com/user-attachments/assets/ce630ab2-da22-4072-a996-7b71ba21637d" /> Release Notes: - rust: Display completion tab stops inline rather than as a raw LSP snippet expression
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- 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.