20554d0296322c64853b18e43d8d39db0da0c45e
Fixes https://github.com/zed-industries/zed/pull/9754#pullrequestreview-2005401133 Fixes https://github.com/zed-industries/zed/pull/9754#issuecomment-2060536590 Closes https://github.com/zed-industries/zed/pull/10669 * Updates the docs to use a proper max value for the centered layout padding (0.4 instead of 0.45) * Makes the `center` wrapper (`h_flex`) to be of size of the `center` element always, to ensure terminal lines are displayed correctly The letter fix is somewhat hacky: while it does the right thing right now, it does not prevent us from future mistakes like these, and does not explain why the bottom dock could be of one, smaller, height, and its contents, the terminal pane/terminal element/something else would think that it has a larger height, thus breaking the scrolling and rendering. cc @alygin if you're interested to solve another layout-related thing. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew tap homebrew/cask-versions
brew install zed-preview
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.
Description
GPUI – Community Edition maintained by Oak Team
https://gpui-ce.github.io/
257 MiB
Languages
Rust
95.5%
WGSL
1.2%
Metal
1.1%
HLSL
1.1%
Python
0.7%
Other
0.3%