Skip to content

Unexpected order of fuzzy find results #103889

@drew-gross

Description

@drew-gross

Version: 1.47.3
Commit: 91899dc
Date: 2020-07-23T13:08:29.692Z (1 wk ago)
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.7.0

Steps to Reproduce:

image

  1. Create a folder with files names managed_object.h.template and generated_types.h.template
  2. Open fuzzy find and type gt.h.template
  3. Expect generated_types.h.template to be found first, instead managed_object.h.template is found first

It's unclear whether this is intentional, and I'm not sure how fuzzy find is intended to work, but coming from Sublime Text, the current behaviour is not very intuitive to me. Sublime Text puts generated_types.h.template first.

image

Does this issue occur when all extensions are disabled?: Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    *as-designedDescribed behavior is as designedfeature-requestRequest for new features or functionalityquick-pickQuick-pick widget issues

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions