Skip to content

Fuzzy search results are not prioritized well. #36166

@thekashifmalik

Description

@thekashifmalik
  • VSCode Version: Code 1.17.1 (1e9d365, 2017-10-10T14:10:17.189Z)
  • OS Version: Darwin x64 16.7.0
  • Extensions:
Extension Author (truncated) Version
postgresql JPT 0.0.2
swift Kas 0.0.3
vscode-docker Pet 0.0.18
project-manager ale 0.21.1
vscode-puppet bit 0.4.5
better-toml bun 0.3.1
path-intellisense chr 1.4.2
vscode-eslint dba 1.3.2
vscode-yaml-validation dja 0.0.1
python don 0.7.0
gitlens eam 5.6.3
tslint eg2 1.0.11
vimL fal 0.0.3
auto-close-tag for 0.5.1
hive-sql jos 0.0.2
vscode-rust kal 0.4.2
restructuredtext lex 38.0.0
Go luk 0.6.66
MagicPython mag 1.0.12
mssql ms- 1.2.0
debugger-for-chrome msj 3.3.1
java red 0.11.0
vscode-icons rob 7.15.0
vscode-nginx sha 0.4.1
slack soz 0.0.13
expand-selection-to-scope vit 0.2.0
vim vsc 0.10.1
jinja who 0.0.8
change-case wma 1.0.0

(1 theme extensions excluded)


I use fuzzy search a lot and after switching to vscode I'm noticing that it's rare for the target file to appear in the top 3 results. It's almost always 10 or 15 results down. Sublime fuzzy search works well as does my setup in vim (using FZF).

Is there a point in having vscode re-invent the wheel and maintain it's own algorithm? Would it be possible to re-use other open source libraries such as FZF?

OSS FTW

Reproduces without extensions: Yes

Metadata

Metadata

Assignees

Labels

quick-pickQuick-pick widget issuessearchSearch widget and operation issues

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions