-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
customCommands enhancement #58
Comments
When would you expect your custom command to appear in the search results? |
At the same time a "shortcut" appears.... |
As a workaround for now: why don't you just set a shorter prefix? |
@oliverschwendener yeah would be max. a compromise solution. Problem is you would have to memorize the prefix. From experience I know that this does not work good... (especially when you have several...) |
Allright. I will look into it as soon as possible. |
I added the possibility to launch custom commands without typing in the full name of the prefix. If you have set up a custom command like this... {
"name": "Open with Visual Studio Code:",
"executionArgument": "!code",
"prefix": "openwithcode"
} ...the custom command appears in the search results when your user input matches the first characters of your prefix. In this example the search result would already appear when typing in This will be included in the next release. |
@oliverschwendener Great, thank you very much... |
You have to write the whole "prefix" of a customCommand plus the the first "variable" part to see anything relevant in the search result:
e.g. I have a definition lke:
I have to type
to see a result
Would it possible to present the command also in the search result? (After selecting in the search result and hit enter or tab the command should be presented in the input area to proceed with the variable part)
The text was updated successfully, but these errors were encountered: