When clipboard data was produced by the editor's copy/cut with multiple entire-line selections, vim's paste would panic with `byte index N is out of bounds`. The editor's `do_copy` and `cut_common` skip the `\n` separator between clipboard selections when the previous selection was an entire-line selection (because the text already ends with `\n`). However, vim's paste code unconditionally did `start_offset = end_offset + 1`, always assuming a `\n` separator exists between every pair of selections. This caused the accumulated offset to exceed the text length, resulting in a string slicing panic. The fix checks `clipboard_selection.is_entire_line` to decide whether to skip the separator, matching the behavior of the editor's own `do_paste` method. The same fix is applied to both the vim and helix paste implementations. Release Notes: - Fixed a crash when using vim paste on clipboard data copied with the editor's copy command containing multiple entire-line selections.
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 issue)
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 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.