a7e26bbfb5
* WIP Start work to send all dap client requests with request_dap * Continue work on converting dap client requests * WIP setup dap command for proto dap requests * WIP dap command Co-authored-by: Remco Smits <djsmits12@gmail.com> * revert "WIP dap command" This reverts commit fd2a6832b667aa23caf588c3ab55243319bc1654. Co-authored-by: Remco Smits <djsmits12@gmail.com> * More WIP with Dap Command trait Co-authored-by: Remco Smits <djsmits12@gmail.com> * Get step over command to work with remote dap clients Co-authored-by: Remco Smits <djsmits12@gmail.com> * Fix thread status not being set to stop on remote debug panel items * Create a inner wrapper type to use for dap remote step requests * Implement step in,back,out for remote debugger sessions * Add Continue Command * Add more dap command impls TerminateThreads, Pause, and Disconnect. As well as a shutdown session request downstream clients can send to host * Add Disconnect & Terminate dap command impls * Add basic dap proxy test over collab * Fix clippy error * Start work on syncing breakpoint thread status Co-authored-by: Remco Smits <djsmits12@gmail.com> Co-authored-by: Carter Canedy <cartercanedy42@gmail.com> * WIP Fix thread status not syncing * Add thread state model's to remote debug panels when setting panel items * Sync thread state on step out command --------- Co-authored-by: Remco Smits <djsmits12@gmail.com> Co-authored-by: Carter Canedy <cartercanedy42@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.