Brandt WearyandHector
e04d044271
## Summary Fixes #33633 - folds corrupting after external file modifications. The existing fold persistence stored raw byte offsets, which become stale when files are modified externally (git operations, other editors, sync tools). This caused folds to capture wrong content on restore - users reported "wrong lines getting folded" with systematic offsets. **Solution: Content fingerprinting** - Store 32-byte content samples at fold boundaries - On restore, validate fingerprints match; if not, search buffer for new positions - Handles edge cases: short folds (< 32 bytes), duplicate content, boundary positioning **Bonus fix: Ungraceful exit survival** - Entity IDs change between sessions, but workspace cleanup's CASCADE DELETE was wiping folds before new editors could save - Now migrates folds to new entity_id immediately after restore ## Test plan - [x] Unit test for fingerprint storage/retrieval (`test_save_and_get_editor_folds_with_fingerprints`) - [x] Manual test: fold sections, add content at file start externally, reopen → folds restore at correct positions - [x] Manual test: fold sections, Ctrl+C, reopen → folds survive - [x] Existing fold tests pass (`cargo test -p editor`) ## Release Notes - N/A --------- Co-authored-by: Hector <hector@cyberneticwilderness.com>
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.