lord
794ad1af75
Some small improvements to OCaml. Would happily split these into smaller changes, discard anything, etc. Before: <img width="441" alt="before" src="https://github.com/user-attachments/assets/2fb82b03-0d45-4c59-a94d-6f48d634fe19"> After: <img width="448" alt="after" src="https://github.com/user-attachments/assets/aa232d8f-4b1b-48f8-93e2-2147de37a20d"> OCaml highlighting and bracketing improvements - Fixed bug where `<` was automatically closed with `>`. - Typing `{|` now automatically closes with `|}` - Type variables are now colored with `variable.special` instead of `variable`. - Argument names in function declarations and application are now colored with `label` instead of `property`, even if they are punned. - `[@@` and `[%` in macros are now colored as bracket punctuation to match the closing `]`, rather than colored as `attribute` Release Notes: - N/A
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.