Forumics logo Forumics
Issue 01

Back to issue

All Zed known issues

CLAIM C154 Supported 2026-11-17

GitHub issue #44855 in zed-industries/zed, opened 2025-12-15 by valderman, records a report that when remote editing, Zed is unable to format a buffer that has not been saved to file: opening a new unsaved file, pasting [1,2,3], setting the language to JSON and formatting leaves the file unchanged instead of formatting it to [1, 2, 3], and the report says this is not exclusive to JSON but also happens with at least Python, SQL and Rust; the report was filed against Zed v0.216.0 stable on Linux Wayland Fedora 43.

Verbatim Excerpts from Cited Records
“Current behavior: file is unchanged.”
— valderman · zed-industries/zed (issue 44855 opening body, Current vs. Expected behavior section) · 2025-12-15T08:58:52Z ·GitHub Issue ↗
“Expected behavior: file is formatted, and now contains `[1, 2, 3]` (note the spaces).”
— valderman · zed-industries/zed (issue 44855 opening body, Current vs. Expected behavior section) · 2025-12-15T08:58:52Z ·GitHub Issue ↗
“This is not exclusive to JSON, but also happens with (at least) Python, SQL and Rust.”
— valderman · zed-industries/zed (issue 44855 opening body, Current vs. Expected behavior section) · 2025-12-15T08:58:52Z ·GitHub Issue ↗
“Open a new file (i.e. NOT preexisting one).”
— valderman · zed-industries/zed (issue 44855 opening body, Reproduction steps section) · 2025-12-15T08:58:52Z ·GitHub Issue ↗
Counter-record: Issue closed 2026-04-10 by github-actions[bot] due to inactivity; 5 comments were read. Zachiah (2025-12-15) reproduced the issue with a video, and yeskunall (2025-12-15) reproduced it and quoted a log warning that Zed cannot format a buffer not backed by a file on disk using language servers. villcabo (2026-11-16) reported the issue was still reproducible on Zed 1.28.1 stable on Linux, and not only when remote editing: it also happens locally whenever the formatter is a language server. No retraction of the original report appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #44855 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.