Change the name in Command Palette to ionide or fsharp (better results for searching)

[sharno]

VSCode mostly shows F results when searching for F# in the command palette. It also feels a lot easier to write fsharp or ionide to reach quickly for a command from the extension.

The photo shows that only the F is being highlighted in the higher results. Also showing that there are many results before the actual extension commands.

[open-collective-bot[bot]]

Hey @sharno 👋,

Thank you for opening an issue. We will get back to you as
soon as we can. Also, check out our OpenCollective and consider
backing us.

https://opencollective.com/ionide

PS.: We offer backer support for all backers. Don't forget to add backer label when you start backing us 😄

[baronfel]

That's not a bad idea. it wouldn't be hard either, just changing a bunch of the contributes.commands entries.

[Krzysztof-Cieslak]

I'm not really sure if I am comfortable with this change - it's a breaking change for the users, it's a longer thing to type, and it's not as obvious as F#. I think a better solution here would be complaining about this issue to the VSCode team. :-)

[sharno]

• I think actually that this is an additive change. It doesn't really break any commands that you write because of the fuzzy search.
• Second is that because VSCode doesn't really consider the # sign in the search, so typing f: run is equal to typing f#: run as you see in the photo it's matching everything including the # sign.
• Lastly, the # sign is really not natural to type while developing in F# and it needs a key combination, so I it doesn't feel really natural while exploring/using the extension to use a key combination while typing in the search bar.

Did I manage to convince you? 😄
(I think even if we file an issue with VSCode itself I'd still prefer to change this in Ionide)

[HerrNiklasRaab]

I agree with @sharno. I am in favor of the name "Fsharp".

[Krzysztof-Cieslak]

Converting this to the discussion rather than issue.

[Krzysztof-Cieslak]

This has been fixed on the VSCode side, and the command palette behaves as expected.