## Bug Before switching macOS appearance: <img width="154" height="39" alt="before switching OS theme" src="https://github.com/user-attachments/assets/2444fafe-21a7-47f6-84ac-ec33a61a6523" /> After switching macOS appearance: <img width="167" height="36" alt="after switching OS theme" src="https://github.com/user-attachments/assets/d4a34555-2964-4e92-8d6a-24da7620fc49" /> After focusing the window following the macOS appearance switch: <img width="151" height="37" alt="after focusing the window after switching the OS theme" src="https://github.com/user-attachments/assets/6bc2e996-256d-448d-a11b-fdc2f0e01f58" /> ## Fix Reapply GPUI's custom macOS traffic-light button position after AppKit reports an effective appearance change and after GPUI's appearance observers have been notified. ## Cause GPUI stores a custom `traffic_light_position` for windows that use transparent/custom titlebars. When macOS switches Light/Dark appearance, AppKit can relayout the standard window buttons, which resets the traffic lights to AppKit's default vertical position. The next normal window focus/layout pass moves them back, causing a visible jump. This change keeps the existing appearance observer callback behavior, then re-runs `move_traffic_light()` after the callback has completed. ## Validation - `cargo check -p gpui_macos --release --features runtime_shaders` - Manually verified with a GPUI window using a transparent titlebar, custom `traffic_light_position`, and an appearance observer that refreshes the window. - Toggled macOS Light/Dark appearance while the window was visible; traffic lights no longer shifted upward. Release Notes: - N/A |
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| typos.toml | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.
- me: do a nixos integration test (using KVM)
- agent: i need to turn off the sandbox
- me: "allow for this thread"
- agent: runs the tests unsandboxed
- me: use the terminal to ls this directory
- agent: runs
lssandboxed