Ben Kunkle
e273de5490
Closes #10832 Note: This PR only fixes the issue where when entering one of `except`, `finally`, `else`, and `elif` after another block like so: ```python try: for i in range(n): pass except:| ``` The `except` would be indented resulting in the following: ```python try: for i in range(n): pass except:| ``` This PR does not fix a separate issue in which the indentation is not corrected from the second example to the first, i.e. if example 2 is typed verbatim in Zed it will not auto-indent to look like example 1. Handling of this case would likely require specific logic to handle, or changes to the tree-sitter grammar for Python, as the current grammar results in ERROR nodes that obscure the natural structure (cannot tie the `except` to the `try`) Release Notes: - Fixed an issue where `except`, `finally`, `else`, and `elif` control flow keywords in Python would be incorrectly indented when entered at the correct level of indentation.
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.