e9b4fa1465
Closes #26124 This PR fixes some more cases of improper attribute highlights for rust. In #25501 I tried to address the regression in highlighting rust attributes which were introduced by #25333 . However, I failed to properly check all cases of attribute highlights as shown in the linked issue - really sorry for that! Thus, this is a follow-up fix aiming to resolve the issues the previous PR did not cover. The changes do not affect any highlighting shown in the [previous PR](https://github.com/zed-industries/zed/pull/25501): | `main` | <img width="719" alt="main-working" src="https://github.com/user-attachments/assets/9aa0e611-7bda-4b50-9335-c87da4c38057" /> | | --- | --- | | This PR | <img width="719" alt="PR-working" src="https://github.com/user-attachments/assets/605b275c-1d68-4bd7-97c6-251d7614a7ed" /> | But resolves the mentioned regressions in the linked issue: | `main` | <img width="371" alt="main_broken" src="https://github.com/user-attachments/assets/ebbb47b7-7945-41e0-b030-2fe3f2198653" /> | | --- | --- | | This PR | <img width="371" alt="PR_broken" src="https://github.com/user-attachments/assets/fa97408b-e1d6-4d99-81c1-cfb8073961a4" /> | Again, sorry for not checking this more thoroughly. Release Notes: - Fixed attributes in Rust being improperly highlighted. Co-authored-by: Marshall Bowers <git@maxdeviant.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.