melon
eecff753fb
Closes #16205 - Updates toolchain.toml - Allows Windows to target the msvc ABI - targetting the gnu toolchain on windows will break key-input since it fails to generate a functional work directory. - errors in question are attached  While the actual issue behind that won't be fixed adding msvc as a toolchain is something that should be done nontheless (and works as a workaround at the moment) one little note: should we specify this in the windows build portion of the Readme (e.g that gnu fails to work properly) or should we fix the underlying problem? the readme has the following content but some people dont use msvc by default (me included) - so this is something that should be mentioned - if wanted i can commit it into this PR or create a new one. > Install [Visual Studio](https://visualstudio.microsoft.com/downloads/) with the optional component MSVC v*** - VS YYYY C++ x64/x86 build tools (v*** is your VS version and YYYY is year when your VS was released) 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.