José Olórtegui
6e2be283dd
Hey guys! `emmet-language-server` author here. Thank you so much for the amazing editor! This PR adds more languages to the list for the `emmet-language-server` to attach to. I have a question though, I saw that you guys don't differentiate yet between `JavaScript` and `JSX` files. I know that the tree-sitter parser for `js` comes with the ability to parse both but we still need to make that difference. Is that part of the plan? or do you have a reason for doing that? Aside from that, I've still added support for `JavaScript` files since is important to have emmet completions in `JSX` files, but I would like to know what are your thoughts on that since doing this may pollute the completions in `.js` files. And one last thing, the emmet language server accepts more filetypes such as `pug`, `sass`, `scss` and `less` files, which are not currently supported by zed. Should I create some extensions to add grammar support to those files later? Should those extensions be part of the zed repo? I'm just thinking that those are sort of core languages. Aside from that, let me know if there's anything left to do on my side. Greetings! Fixes #10654. Release Notes: - N/A
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.