Tim VermeulenandJoseph T. Lyons
42ef3e5d3d
Fixes two inconsistencies around the behavior of cmd-alt-click that mess with my VSCode muscle memory: - The definition is opened in a pane to the right of the current pane, unless there exists an adjacent pane to the left and not to the right, in which case it's opened in the pane on the left - In case Go to Definition needs to open a multibuffer, cmd-alt-click does not open it in an existing pane to the right of the current pane, it always creates a new pane directly to the right of the current pane This PR irons out this behavior by always going to the definition in the pane directly to the right of the current one, creating one only if one doesn't yet exist. If changing `Workspace::adjacent_pane` to not consider an existing pane to the left is undesirable then that logic could be moved somewhere else, or we can make it user configurable if necessary. Also happy to split this PR up if either of these changes is controversial 🙂 Before: https://github.com/user-attachments/assets/395754cd-6ecb-40bf-ae61-ee8903eed4ae After: https://github.com/user-attachments/assets/002797b1-51a7-48e5-a8d0-100d3a5049eb Release Notes: - Made the behavior of cmd-alt-click more consistent --------- Co-authored-by: Joseph T. Lyons <JosephTLyons@gmail.com>
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.