842bf0287d
* Use buffer settings for font, size etc. * Trim end of message * By default send the output values to the output editor * WIP send evaluate request * Rename variable * Add result to console from evaluate response * Remove not needed arc * Remove store capabilities on variable_list * Specify the capacity for the task vec * Add placeholder * WIP add completion provider for existing variables * Add value to auto completion label * Make todo for debugger * Specify the capacity of the vec's * Make clippy happy * Remove not needed notifies and add missing one * WIP move scopes and variables to variable_list * Rename configuration done method * Add support for adapter completions and manual variable completions * Move type to variabel_list * Change update to read * Show debug panel when debug session stops Co-Authored-By: Anthony Eid <56899983+Anthony-Eid@users.noreply.github.com> Co-Authored-By: Mikayla Maki <mikayla.c.maki@gmail.com> * Also use scope reference to determine to which where the set value editor should display * Refetch existing variables after * Rebuild entries after refetching the variables --------- Co-authored-by: Anthony Eid <56899983+Anthony-Eid@users.noreply.github.com> Co-authored-by: Mikayla Maki <mikayla.c.maki@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.