Finn Evers
042fc82e99
Closes #25803 Closes #25707 This PR fixes the highlighting regression described in #25803 by fixing the priorities of highlights as described in the [comment within the file itself](https://github.com/zed-industries/zed/blob/5b66ea15638b004c45bbf4e4dd0b576aa6cdcebc/crates/languages/src/python/highlights.scm#L1). A nice side-effect of this is that scoped constants or other identifiers are now also more accurately highlighted, as seen in the screenshots below. While I was at it, I also adressed the highlighting issue for default typed idenfiers. | This PR | <img width="575" alt="PR" src="https://github.com/user-attachments/assets/aed5cdd0-c31a-4794-8128-376944fddd2d" /> | | --- | --- | | Preview | <img width="575" alt="preview" src="https://github.com/user-attachments/assets/ae3fad35-d436-472c-aff0-16508304ccf7" /> | | Stable | <img width="575" alt="stable" src="https://github.com/user-attachments/assets/3836427c-f1cc-42ea-b1a7-8f5bbbadf210" /> | Release Notes: - Fixed constants not being highlighted in Python-files. - Improved Python-highlighting for default function arguments and scoped identifiers.
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.