e1063743e8
Closes #43963 This issue was caused by the global marks not being deleted. Previously marking the first file `m A` <img width="1736" height="888" alt="Screenshot From 2025-12-13 01-37-55" src="https://github.com/user-attachments/assets/9e46747f-7bb3-4297-82d4-44a20ef9e91a" /> followed by marking the second file `m A` <img width="1736" height="888" alt="Screenshot From 2025-12-13 01-37-42" src="https://github.com/user-attachments/assets/0d126b47-2c42-475f-826a-173c0d5a1156" /> and navigating back to the first file <img width="1736" height="888" alt="Screenshot From 2025-12-13 01-37-30" src="https://github.com/user-attachments/assets/032fd0bd-ff71-4a12-987a-7f1743016f6d" /> shows that the mark still exists and was not properly deleted. After these changes the global mark in the original file is correctly overwritten. Added regression test for this. Release Notes: - Fixed bug where overwriting global Vim marks was inconsistent
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.
Other platforms are not yet available:
- Web (tracking issue)
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.