Sean Billig
be2df79d5c
`[NSString UTF8String]` sometimes returns null (it's documented as such), and when it does, zed crashes in `window::insert_text`. I'm running into this sometimes when using alt-d to delete forward. It usually only happens with multiple cursors, but sometimes with a single cursor. It *might* only happen when using the "Unicode Hex Input" keyboard 'Input Source' (which I started using to avoid entering weird characters in zed when using emacs meta keybindings that I haven't defined in zed). When using the US English input source, alt-d always results in a call to `insert_text`. When using the Unicode Hex Input source it usually doesn't, but when it does `text.UTF8String()` returns null. `text` isn't null. `[text length]` returns 1. `[text characterAtIndex: 0]` seems to always return `56797` (an undefined utf-16 codepoint). Release Notes: - Fixed crash on mac when deleting with alt-d
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
You can download Zed today for macOS (v10.15+).
Support for additional platforms is on our roadmap:
- Linux (tracking issue)
- Windows (tracking issue)
- Web (tracking issue)
For macOS users, you can also install Zed using Homebrew:
brew install --cask zed
Alternatively, to install the Preview release:
brew install --cask zed@preview
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.