Finn EversandBeniamin Zagan
f2b7d8a9c9
Closes #24565 As pointed out in https://github.com/zed-industries/zed/issues/24565#issuecomment-2657822723 , the name for the Pyright language server is `pyright-langserver`, not `pyright`. The latter is a CLI-tool as described in https://microsoft.github.io/pyright/#/command-line which only provides static type checking. It has neither LSP-capabilities nor a `--stdio` argument. Thus, the error as shown in the linked issue appears. I disagree with the fix as described in https://github.com/zed-industries/zed/issues/24565#issuecomment-2657904208 , as it could only cause this error to reappear in rare scenarios where Pyright, but not the Pyright language server is installed in a user's environment. Just checking for `pyright-langserver` to be present in the environment seems more straightforward here. Release Notes: - Python: Fixed Pyright failing to start when installed locally Co-authored-by: Beniamin Zagan <47153906+beniaminzagan@users.noreply.github.com>
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.