Luke NaylorandPeter Tripp
522abe8e59
Closes: https://github.com/rzukic/zed-latex/issues/77 ## Default formatter: `latexindent` Before, formatting was delegated to the language server, which just ran a `latexindent` executable. There was no benefit to running it through the language server over running it as an "external" formatter in zed. In fact this was an issue because there was no way to provide an explicit path for the executable (causing above extension issue). Having the default settings configure the formatter directly gives more control to user and removes the number of indirections making it clearer how to tweak things like the executable path, or extra CLI args, etc... ## Alternative: `prettier` Default settings have also been added to allow prettier as the formatter (by just setting `"formatter": "prettier"` in the "LaTeX" language settings). This was not possible before because an extra line needed to be added to the `prettier` crate (similarly to what was done for https://github.com/zed-industries/zed/issues/19024) to find the plugin correctly. > [!NOTE] > The `prettier-plugin-latex` node module also contained a `dist/standalone.js` but using that instead of `dist/prettier-plugin-latex.js` gave an error, and indeed the latter worked as intended (along with its questionable choices for formatting). Release Notes: - LaTeX: added default `latexindent` formatter settings without relying on `texlab`, as well as allowing `prettier` to be chosen for formatting --------- Co-authored-by: Peter Tripp <peter@zed.dev>
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.