Beniamin Zagan
2d6592dcaa
On macos: - user has the required permission to screen share. - user doesn't have the can_use_microphone permission When an user doesn't have the can_use_microphone permission the screen share icon would be visible. If an user therefor would click on it, we would give the error that they don't have the permission given to zed to screen share. (which is false). I've tested this together with @JosephTLyons because we first thought it was a mac os permission issue. Should we mention in the zed.dev/docs/collaboration what kind of permissions are needed to be able to screen share? Release Notes: - Fixed: Screen sharing would be visible even when user didn't have the right permission resulting in errors later on.
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.