Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
Kirill Bulatov b6b87405b0
Some checks are pending
CI / check_docs_only (push) Waiting to run
CI / Check Postgres and Protobuf migrations, mergability (push) Waiting to run
CI / Check formatting and spelling (push) Waiting to run
CI / (macOS) Run Clippy and tests (push) Blocked by required conditions
CI / (Linux) Run Clippy and tests (push) Blocked by required conditions
CI / (Linux) Build Remote Server (push) Blocked by required conditions
CI / (Windows) Run Clippy and tests (push) Blocked by required conditions
CI / Create a macOS bundle (push) Blocked by required conditions
CI / Create a Linux bundle (push) Blocked by required conditions
CI / Create arm64 Linux bundle (push) Blocked by required conditions
CI / Auto release preview (push) Blocked by required conditions
Deploy Docs / Deploy Docs (push) Waiting to run
Docs / Check formatting (push) Waiting to run
Script / ShellCheck Scripts (push) Waiting to run
Do not try to activate the terminal panel twice (#23029)
Closes https://github.com/zed-industries/zed/issues/23023

Fixes terminal pane button opening two terminals on click.

The culprit is in

61115bd047/crates/workspace/src/workspace.rs (L2412-L2417)

* We cannot get any panel by index from the Dock, only an active one
* Both `dock.activate_panel(panel_index, cx);` and `dock.set_open(true,
cx);` do `active_panel.panel.set_active(true, cx);`

So, follow other pane's impls that have `active: bool` property for this
case, e.g.
3ec52d8451/crates/assistant/src/inline_assistant.rs (L2687)

Release Notes:

- Fixed terminal pane button opening two terminals on click
2025-01-12 12:56:31 +00:00
.cargo
.cloudflare
.config
.github ci: Install cargo-nextest with --locked (#22984) 2025-01-10 21:27:28 +00:00
.zed
assets zeta: Show keybinding in completion rating buttons in review modal (#22985) 2025-01-10 22:00:11 +00:00
crates Do not try to activate the terminal panel twice (#23029) 2025-01-12 12:56:31 +00:00
docs docs: Fix "copy" being used instead of "paste" in vim mode documentation (#23010) 2025-01-11 21:45:41 +00:00
extensions csharp: Add brackets.scm (#22936) 2025-01-10 16:18:33 +00:00
legal Stop sending data to Clickhouse (#21763) 2024-12-10 08:47:29 -07:00
nix nix: Fix webrtc-sys and libstdc++ build errors in development shell (#22938) 2025-01-10 12:50:33 +00:00
script Fix script/bump-zed-minor-versions. Revert #22834 Revert #22614 (#22837) 2025-01-08 10:59:30 -05:00
tooling/xtask
.git-blame-ignore-revs
.gitattributes
.gitignore
.mailmap
Cargo.lock zeta: Report Fireworks request data to Snowflake (#22973) 2025-01-10 22:40:54 +00:00
Cargo.toml zeta: Report Fireworks request data to Snowflake (#22973) 2025-01-10 22:40:54 +00:00
clippy.toml
CODE_OF_CONDUCT.md
compose.yml
CONTRIBUTING.md
Cross.toml
debug.plist
default.nix
docker-compose.sql
Dockerfile-collab
Dockerfile-collab.dockerignore
Dockerfile-cross
Dockerfile-cross.dockerignore
Dockerfile-distros
Dockerfile-distros.dockerignore
flake.lock Fix nix shell (#22091) 2025-01-07 04:03:22 +00:00
flake.nix
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
livekit.yaml
Procfile
Procfile.postgrest
README.md
renovate.json
rust-toolchain.toml
shell.nix
typos.toml clojure: Extract to zed-extensions/clojure repository (#22628) 2025-01-03 21:14:53 +00:00

Zed

CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

Packaging status

On macOS and Linux you can download Zed directly or install Zed via your local package manager.

Other platforms are not yet available:

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

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, add publish = 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.