Ben Kunkle
fc920bf63d
Closes #28414 Makes it so that `do`, `then`, `done`, `else`, etc are treated as brackets in bash. They are not auto-closed *yet* as that requires additional work to function properly, however they can now be toggled between using `%` in vim. Additionally, newlines are inserted like they are with regular brackets (`{}()[]""''`) when hitting enter between them. While `if <-> fi` `while/for <-> done` and `case <-> esac` are the *logical* matching pairs, I've opted to instead match between `then <-> else/elif/fi` `do <-> done` and `in <-> esac` as these are the pairs that delimit the sub-scope, and are more similar to the `{}` style bracket pairs than `if <-> }` in a c-like syntax. This does cause some wierd behavior with `else` in `if` expressions as it matches both with the previous `then` as well as the following `fi`, so in this case ```bash if true; then foo else bar f|i ``` after hitting `%` twice times (where cursor is `|`), the cursor will end up on the `then` instead of back on the `fi` as hitting `%` on the else will *always* navigate up to the `then` Release Notes: - vim: Improved behavior around word-based delimiters in bash (`do <-> done`, `then <-> fi`, etc) so they can be toggled between using `%`
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.