Skip to content
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

Closed
maku opened this issue Sep 19, 2018 · 7 comments
Closed

customCommands enhancement #58

maku opened this issue Sep 19, 2018 · 7 comments

Comments

@maku
Copy link

maku commented Sep 19, 2018

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:

"customCommands": [
    {
      "name": "Open with Visual Studio Code:",
      "executionArgument": "!code",
      "prefix": "openwithcode"
    }
  ],

I have to type

image

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)

@oliverschwendener
Copy link
Owner

When would you expect your custom command to appear in the search results?

@maku
Copy link
Author

maku commented Sep 20, 2018

At the same time a "shortcut" appears....

@oliverschwendener
Copy link
Owner

As a workaround for now: why don't you just set a shorter prefix?

@maku
Copy link
Author

maku commented Sep 26, 2018

@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...)

@oliverschwendener
Copy link
Owner

Allright. I will look into it as soon as possible.

@oliverschwendener
Copy link
Owner

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 open or even o.

This will be included in the next release.

@maku
Copy link
Author

maku commented Oct 9, 2018

@oliverschwendener Great, thank you very much...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants