Matthias Grandl
4024b9ac4d
Release Notes: - N/A While developing [Loungy](https://loungy.app), I noticed that everytime I wake my laptop, Loungy starts consuming 100% CPU. I traced it down to `start_display_link` as there was this error message at the time of wake up: ``` [2024-05-02T05:02:31Z ERROR util] /Users/matthias/zed/crates/gpui/src/platform/mac/window.rs:420: could not create display link, code: -6661 ``` The timeline is this: 1. The application is hidden with `cx.hide()` 2. The system is put to sleep and later woken up 3. `window_did_change_screen` would trigger immediately after wakeup, calling `start_display_link` 4. `start_display_link` fails catastrophically as `DisplayLink::new` starts hogging all the CPU for some reason? 5. throws the error message above 6. Once the window is opened, `window_did_change_occlusion_state` it retriggers `start_display_link` and the CPU issue subsides
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 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.