<spc> s s and <spc> s S behavior about vspacecode

[sutram]

@stevenguh I did restart vscode. Here is the interesting thing:

From the command palette, I only see "Fuzzy outline" and if I go and check the fuzzy extension, the only command that is exposed by that extension is fuzzySearch.activeTextEditor with a description of "Fuzzy outline"

Thanks

[stevenguh]

Make sure jacobdufault.fuzzy-search extension is installed. It should be automatically installed by vscode since this extension is an extension pack that bundles that; however, it might not.

Also, is there any chance you are running vscode remote?

[stevenguh]

I just realized is a bug I introduced with <spc> s s as it didn't call the right command

[stevenguh]

Released v0.7.2 to fix the issue where <spc> s s wasn't calling the right command.

[sutram]

@stevenguh That was a quick release! 😄

I tried 0.7.2 and now with s s, I get the same error: TaskQueue: Error running task. Failed to handle key= . command 'fuzzySearch.activeTextEditorWithCurrentSelection' not found.

s S also results in the same error: TaskQueue: Error running task. Failed to handle key= . command 'fuzzySearch.activeTextEditorWithCurrentSelection' not found.

I checked and I have fuzzy-search 0.0.2 by jacobdufault installed

Thanks!

[sutram]

@stevenguh Sorry, also forgot to answer your other question - I am not editing a remote file. This is a local file

[stevenguh]

Can you try using the command palette (Ctrl+Shift+P) to search fuzzySearch.activeTextEditorWithCurrentSelection to see if you can see and trigger the command manually.

Also, have you tried restarting/reloading vscode?

[stevenguh]

This is very interesting. I figured it out, apparently for some reason VSCode cached a development version on my local vscode instance which contains that command. The current latest version v0.0.2 of fuzzy search doesn't contain that command. I opened an issue in the repo, and hopefully we will get a new release soon. Worst case, we might have to fork the repo and release it under VSpaceCode org.
jacobdufault/vscode-fuzzy-search#11

Meanwhile, merge this into your settings.json to override the default command

{
  "vspacecode.bindingOverrides": [
    {
      "keys": "s.s",
      "name": "Fuzzy search",
      "type": "command",
      "command":"fuzzySearch.activeTextEditor",
    }
  ]
}

[sutram]

@stevenguh s s is working with that workaround. I noticed that the developer was active 10 days ago so maybe there is a possibility of fuzzy match with selection.

[stevenguh]

The author of the fuzzy-search released v0.0.3. It should fix this issue and you can undo the override workaround.