7d1cb8b072
<img width="447" alt="SCR-20240121-ofhg" src="https://github.com/zed-industries/zed/assets/19867440/7fe13a74-45c7-43ec-a5e8-5127bc285b32"> In this screenshot, the first two messages were sent back-to-back, but the third message was sent nearly two hours later. Coalescing the messages doesn't feel right after a certain period of time, as it gives misleading timestamps on messages. Discord has this feature, but I'm not sure what the value they use is. I've set the threshold to 5 minutes for now. <img width="480" alt="SCR-20240121-oghs" src="https://github.com/zed-industries/zed/assets/19867440/ee1cfe36-7c13-4072-9f66-93e2de6542f1"> Release Notes: - Improved the grouping of chat messages from same user. Grouping now only occurs if the user sends multiple messages, in succession, within a specified duration of time.
🚧 TODO 🚧
- Add intro
- Add link to contributing guide
- Add barebones running zed from source instructions
- Link out to further dev docs
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Developing Zed
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.