acbc42cdb7
This fixes the problem described in #15023 by allowing extensions to designate language servers as secondary language servers. Secondary language servers can be used for formatting/linting/diagnostics, but they won't be used for go-to-definition and find-references. The problem before this change was that extension authors and users didn't have any influence on which language server is used as the primary or secondary language server. Since they were all designated as "primary", Zed would pick the first one in the list of running language servers. And the order of entries in that' list is dependent on the order in which the language servers were started. We could somehow steer this behaviour through the order and, when trying to find a primary language server, traverse the list in the order of the language servers as they are defined in the settings, but that seems brittle. We'd have to ensure that users have their language server entries ordered correctly and "teach" them about primary vs. secondary language servers. Instead, we can leave it up to the extension authors to decide which server can act as a primary language server and which as a secondary. In the case of rubocop, too, I think it's pretty clear-cut that it's a secondary language server, like tailwind or ESLint.
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.