Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 2
    Thanks for that. I kept trying to find a "type" for the command. It never occurred to me to just leave that out. Your example worked perfectly. Unfortunately, it doesn't seem to recognize commands from add-ons such as: command:extention.liveServer.goOnline Commented Aug 13, 2019 at 20:41
  • 2
    Hmm, that is why I tried it with extension.gist.open a command from an installed extension and it worked just fine. It seems to work with/without the shell/process type for me. Did you try both versions with your command? It might need process for example. Commented Aug 13, 2019 at 21:23
  • Okay, I'm an idiot. I misspelled "extension", thank you Mark :) Commented Aug 15, 2019 at 14:09
  • If the command has some output, and you're using that task as a build task, VSCode might try to execute the output. For example, ${command:tinymist.exportCurrentPdf} will be replaced with the exported PDF's path. In this case, you can use "type": "shell" together with "args" to prevent this behavior: "label": "Tinymist: Export current PDF", "type": "shell", "command": "echo", "args": ["${command:tinymist.exportCurrentPdf}"] Commented Dec 23, 2024 at 6:30
  • I'm wondering if it's also possible to pass arguments to the command. Commented Jul 17 at 17:37