Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can searching for *an exact matching path* NOT be the first (single) result?!? #1971

Open
stdedos opened this issue Oct 24, 2024 · 1 comment

Comments

@stdedos
Copy link

stdedos commented Oct 24, 2024

Version info

  • OS: [e.g. macOS 10.14, Windows 10, Ubuntu 18.04]
  • Build: [e.g. 1062 - type "About" in the command palette]

Description

A description of what the bug is.

image

Steps to reproduce

Steps to reproduce the behavior:

  1. Open repository ...
  2. Run command ...
  3. Click on ...

Expected behavior

A description of what you expected to happen.

Debug Information
The Sublime Merge debug information can be used to narrow down the cause of an issue.
It can be collected with the following steps:

  1. Open Sublime Merge
  2. Open the repository where the bug occurs
  3. Navigate to Help > Debug Information via the application menu
  4. Before sharing, please redact any information that's sensitive such as file paths, git user information, remote URLs etc.

This section may be omitted/removed.

Screenshots

If applicable, add screenshots to help explain your problem. This section may be omitted/removed.

@stdedos stdedos changed the title How can searching for *an exact matching path* NOT be the first result?!? How can searching for *an exact matching path* NOT be the first (single) result?!? Oct 24, 2024
@dpjohnst
Copy link
Member

Hi @stdedos,

Thanks for reaching out and sharing this feedback!

Currently the search results are ordered by alphanumeric sorting, and not by match ranking.
This definitely something I plan on adding, and I'll keep you updated on the progress of this.

Kind regards,
- Dylan from Sublime HQ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants