tims
e25789893d
Closes #22607 Symlinks can be absolute or relative. When using [stow](https://www.gnu.org/software/stow/) to manage dotfiles, it creates relative symlinks to the target files. For example: - Original file: `/home/tims/dotfiles/zed/setting.json` - Symlink path: `/home/tims/.config/zed/setting.json` - Target path (relative to symlink): `../../dotfiles/zed/setting.json` The issue is that you can’t watch the symlink path because it’s relative and doesn't include the base path it is relative to. This PR fixes that by converting relative symlink paths to absolute paths. - Absolute path (after parent join): `/home/tims/.config/zed/../../dotfiles/zed/setting.json` (This works) - Canonicalized path (from absolute path): `/home/tims/dotfiles/zed/setting.json` (This works too, just more cleaner) Release Notes: - Fix issue where items on the Welcome page could not be toggled on Linux when using Stow to manage dotfiles
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.