mirror of
https://github.com/zed-industries/zed.git
synced 2024-10-23 14:59:50 +00:00
Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
8524e87319
We saw this panic come up: ``` called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: UnknownError }) core::panicking::panic_fmt core::result::unwrap_failed <gpui::platform::linux::x11:🪟:X11Window as core::ops::drop::Drop>::drop core::ptr::drop_in_place<gpui::platform::linux::x11:🪟:X11Window> core::ptr::drop_in_place<gpui:🪟:Window> gpui::app::AppContext::shutdown gpui::app::AppContext:🆕:{{closure}} gpui::platform::linux::platform::<impl gpui::platform::Platform for P>::run gpui::app::App::run zed::main std::sys_common::backtrace::__rust_begin_short_backtrace std::rt::lang_start::{{closure}} std::rt::lang_start_internal main __libc_start_call_main __libc_start_main_impl _start ``` I'm not sure where exactly that error comes from, except from the X11 stuff. So let's be defensive and log error and only then tear down everything. I _think_ that if the error is repeatable that means we won't close the window but instead just log errors, but I do think that's better than panicking right now. Release Notes: - N/A |
||
---|---|---|
.cargo | ||
.cloudflare | ||
.config | ||
.github | ||
.zed | ||
assets | ||
crates | ||
docs | ||
extensions | ||
script | ||
tooling/xtask | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
Cargo.lock | ||
Cargo.toml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
debug.plist | ||
docker-compose.sql | ||
docker-compose.yml | ||
Dockerfile | ||
LICENSE-AGPL | ||
LICENSE-APACHE | ||
LICENSE-GPL | ||
livekit.yaml | ||
Procfile | ||
README.md | ||
rust-toolchain.toml | ||
typos.toml |
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 install --cask 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 specified
error for a crate you've created? If so, addpublish = false
under[package]
in your crate's Cargo.toml. - Is the error
failed to satisfy license requirements
for 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 theaccepted
array inscript/licenses/zed-licenses.toml
. - Is
cargo-about
unable 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.