mirror of
https://github.com/zed-industries/zed.git
synced 2026-10-19 11:04:06 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
b0d4fd203d
# Objective Fixes #64159 `ENABLE_YAML_STYLE_METADATA_BLOCKS` is enabled for the whole document whenever metadata rendering is on. pulldown-cmark then treats any unindented `---` line followed later by another `---` as a metadata block, so ordinary section separators in Markdown Preview and the Agent Panel swallowed the text between them and rendered it as a code-style box. ## Solution Frontmatter only exists at the start of a file, so the parser now: - probes with the YAML option only when the document starts with `---`, and keeps the first block if pulldown-cmark reports a YAML metadata block there; - parses the rest of the document with the YAML option off; - shifts the body's event ranges and link definition spans back to offsets in the original text. ## Testing - `test_yaml_frontmatter_does_not_consume_body`: frontmatter in LF, CRLF, and `...`-closed forms, and none at all. Checks that both body separators are rules, the section between them keeps its heading, bold text, and reference link, and that every event range and heading offset still points into the original text. - `test_body_separators_are_not_yaml_metadata`: parsing with metadata rendering on and off must give identical results for separators in the body, inside a blockquote, inside a list item, and after a leading blank line. ## Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content adheres to Zed's UI standards ([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) and [icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md) guidelines) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable ## Showcase The theme differs in the two screenshots because the "After" one was taken in a local dev build with default settings. Only the rendering of the `---` sections is relevant. Before: <img width="675" height="505" alt="Screenshot 2026-09-13 at 22 30 49" src="https://github.com/user-attachments/assets/2df3d95d-23c9-46a5-9278-53c3894135a0" /> After: <img width="610" height="421" alt="Screenshot 2026-09-13 at 22 29 08" src="https://github.com/user-attachments/assets/d616c46c-95cc-408d-99a1-70f1f8d3c4b4" /> --- Release Notes: - Fixed Markdown Preview and the Agent Panel rendering the text between two `---` separators as a YAML metadata block. --------- Co-authored-by: Kirill Bulatov <kirill@zed.dev> |
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .wezel | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| corgi.toml | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| Procfile | ||
| Procfile.web | ||
| README.md | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
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 discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.