2e56935997
Closes #25941 Release Notes: - Corrected SoftTab indentation handling for lines with mixed spaces and tabs across .go files and other file types. - Renamed the editor test `test_tab_with_mixed_whitespace` to `test_tab_with_mixed_whitespace_rust` as it only tested this behavior for Rust buffers, which have auto-indentation support. This change clarifies that the test does not cover default files without language-specific features. - Added a new editor test `test_tab_with_mixed_whitespace_txt` to ensure proper coverage for files with no associated language. While investigating the issue — initially thought to be Go-related — I discovered that the underlying problem was how soft tabs were calculated in `Editor::tab`, given that the problem could also be observed on `.txt` files The correct soft tab indentation is now determined by treating all `\t` characters before the cursor (on the same row) as new indentation levels, resetting the remainder counter accordingly. https://github.com/user-attachments/assets/78192e98-2b81-43cb-ae6f-7c48cd17d168
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- 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.