Peter Tripp
9a3720edd3
This disables word based completions in Plain Text and Markdown buffers by default. Word-based completion when typing natural language can be quite disruptive, in particular at the end of a line (e.g. markdown style lists) where `enter` will accept word completions rather than insert a newline (see screenshot). I think the default, empty buffer experience in Zed should be closer to a zed-mode experience -- just an editor getting out of your way to let you type and not having to mash escape/cmd-z repeatedly to undo a over-aggressive completion. <img width="265" alt="Screenshot 2025-07-08 at 11 57 26" src="https://github.com/user-attachments/assets/131f73a8-4687-45bf-ad53-f611c0af9387" /> - Context: https://github.com/zed-industries/zed/issues/4957#issuecomment-3049513501 - Follow-up to: https://github.com/zed-industries/zed/pull/26410 Re-enable the existing behavior with: ```json "languages": { "Plain Text": { "completions": { "words": "fallback" } }, "Markdown": { "completions": { "words": "fallback" } }, }, ``` Or disable Word based completions everywhere with: ```json "completions": { "words": "fallback" }, ``` Release Notes: - Disable word-completions by default in Plain Text and Markdown Buffers
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.