Danilo LealandMarshall Bowers
5e04753d1c
When pressing <kbd>control</kbd> + <kbd>enter</kbd>, the AI-powered inline transformation input displays an icon button and a token count, which should show roughly the same numbers you'd see on your assistant panel. At a first glance, though, the token count not being zero can be confusing, where you'd wonder where that's coming from. That's because the inline input uses whatever piece of context and/or information of the currently selected assistant tab to suggest more accurate edits. So, this PR introduces an informative piece of text to the `ModelSelector` menu, on the inline transformation input, which delivers exactly this bit of info, aimed at clarifying the connection between these two methods of interacting with LLMs. I've also took the opportunity to change the icon button's icon to one that's a bit easier to see, still representing the affordance of "click to configure something". Release Notes: - Add note about how inline edits consume context from the assistant panel to clarify interaction with LLMs. --------- Co-authored-by: Marshall Bowers <elliott.codes@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.