Ivan Trubach
aec3c2fbb7
Currently, <kbd>⌃w</kbd> + <kbd>HJKL</kbd> keystrokes swap active pane with another pane in that direction. Also, if there is no pane to swap with, nothing happens. This does not match the expected Vim behavior: moving the split to span the entire border. See https://github.com/vim/vim/blob/ca6a260ef1a4b4ae94bc71c17cbabf8f12bf0f8c/runtime/doc/windows.txt#L527-L549 This change adds `MovePane{Up,Down,Left,Right}` actions that do exactly that and updates default Vim keymap. <table> <tr> <th>Before</th> <th>After</th> <tr> <td><video src="https://github.com/user-attachments/assets/5d3a25bf-e8b6-46c1-9fbb-004f0194e0dd"> <td><video src="https://github.com/user-attachments/assets/5276f115-5063-411e-b141-5d268a79581b"> <tr> <th>Vim</th> <tr> <td><video src="https://github.com/user-attachments/assets/df9fbf83-d0de-42c0-8fb0-b134be833bde"> </table> Release Notes: - Changed `ctrl+w` + `shift-[hjkl]` in Vim mode to move the split to span the entire border, aligning with Vim‘s behavior. Signed-off-by: Ivan Trubach <mr.trubach@icloud.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- 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.