Finn Evers
0119b66426
Closes #29858 This PR fixes the alignment-issue for the project saerch for cases where the horizontally available space is large. The issue arose because the two smaller editors within one line were allowed to grow as much as the other editors on separate lines, up to 1200 pixels. However, these two editors should together only take up 1200 pixels at maximum, including the gap between them. To fix this, the editors now live within one container element that grows at the same rate as the other editors whilst allowing both editors to flex grow as needed in the available space. Current main: https://github.com/user-attachments/assets/622016dc-70e5-455f-a7ba-5b69405d7e1e This PR: https://github.com/user-attachments/assets/5244abf7-f0c0-4781-acb7-b774638d8a17 Release Notes: - Improved project search input field alignment.
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.