Thorsten Ball
5de5d5bc56
This fixes #14818. The change in #14055 broke the tasks in `zsh` (and I suspect in `bash`, `sh` too), because what was executed was NOT $ go test . -run '^TestThis$' but instead this: $ go test . -run \'^TestThis$\' And in `zsh` this means that `'` is part of the argument passed to `go`, which means the targeting string is wrong. Since the problem in `fish` doesn't seem to be the `^` but the `$`, we can only escape that, which makes the escaped string work in `zsh` and `fish` and `bash` (in which I've tested this change here) Release Notes: - go: Fix running single tests by changing the quoted expression in the `go test` command to work again in `bash`, `zsh`, etc. ([#14818](https://github.com/zed-industries/zed/issues/14818))
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.