604d56659d
These changes update the way the file finder decides wether to only look for an absolute path or for a relative path too. When the provided query started with a slash (`/`) the file finder would assume this to be an absolute path so would always try to find an absolute path and return no matches if none was found. This is meant to support situtations where, for example, a CLI tool might output the absolute path of a file and the user can copy and paste that in the file finder. However, it's should be possible to use slash (`/`) at the start of the query to specify that only relative files inside a folder should be matched, which would not work in this scenario. With these changes, the file finder will first check if the path is absolute and, if it is and no absolute matches were found, it'll still try to find relative matches, otherwise it'll simply look for relative matches. Closes #39350 Release Notes: - Fixed project files matches when using slash (`/`) at the start in order to consider relative paths --------- Co-authored-by: Piotr Osiewicz <piotr@zed.dev> Co-authored-by: Piotr Osiewicz <24362066+osiewicz@users.noreply.github.com>
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.