Smit Barmase
67f9da0846
Closes #27631 We use `widest_completion_ix` to figure out completion menu width. This results in flickering between frames as more information about completion items, such as signatures, is populated asynchronously. There is no way to know this width or which item will be widest beforehand. While using a hardcoded value feels like a backward approach, it results in a far smoother experience. VSCode also uses fixed width for completion menu. Before: https://github.com/user-attachments/assets/0f044bae-fae9-43dc-8d4a-d8e7be8be6c4 After: https://github.com/user-attachments/assets/21ab475c-7331-4de3-bb01-3986182fc9e4 Release Notes: - Fixed issue where code completion menu would flicker while typing.
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.