Danilo Leal
d0ca49f0e1
Closes https://github.com/zed-industries/zed/issues/13099 This PR main thing is making the inputs in the project search full width, but it also has some slight design and UI code improvements here and there, such as extracting the common input styles to its own variable. I figure that the reason why the inputs weren't full width before is just because it'd be hard to reach for the buttons when in a large monitor with the app maximised _and_ with a single tab open. However, I do feel like it's common not to have these conditions in place, too, which make the small inputs too small, like the issue states. At the very least, we also have the keybindings. Here's the final result: | Small window size | Big window size | |--------|--------| | <img width="1279" alt="Screenshot 2024-11-05 at 11 18 08" src="https://github.com/user-attachments/assets/73548300-1ad2-4ed0-b99f-adb3212ac163"> | <img width="2992" alt="Screenshot 2024-11-05 at 11 24 06" src="https://github.com/user-attachments/assets/3a1ccabd-2350-42f0-8e31-112f27da98a4"> | Release Notes: - N/A
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.