You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tasks can now be executed in the terminal instead of the Output window. To enable this you need to add a global property "_runner": "terminal" to the tasks.json file.
Executing a task in a terminal should work as executing a task in the output windows including problem matcher, watching task (now named background tasks) and commands per task. When a task is executed in the terminal you get the additional features:
output encoding plus full ANSI character support (comes for free from the terminal)
input (the task can read from stdin) (comes for free from the terminal)
you can run more than one task in parallel.
control over the shell to be used.
Please test that all the features available in the 'output' runner work in the 'terminal' runner plus the newly mentioned features. Try to kill a n active task F1 > task terminate. The terminal runner tries to reuse terminals. Ensure that the reuse strategy makes sense. Play a little with task executed in the terminal. If you have ideas, please let me know. Executing them in the terminal opens new use cases.
Please also note that due to a problem in the terminal command quoting when executed in a shell doesn't work as expected. So a command like "dir "folder with spaces"" is not correctly executed in a cmd.exe run in the terminal. See #19078 for details:
The first task executes the tsc compiler in watch mode (assumes it is available globally). The second one executes the dir command using a special shell path for the terminal.
The text was updated successfully, but these errors were encountered:
Refs: #18312
Complexity: 3
Tasks can now be executed in the terminal instead of the
Output
window. To enable this you need to add a global property"_runner": "terminal"
to the tasks.json file.Executing a task in a terminal should work as executing a task in the output windows including problem matcher, watching task (now named background tasks) and commands per task. When a task is executed in the terminal you get the additional features:
Please test that all the features available in the 'output' runner work in the 'terminal' runner plus the newly mentioned features. Try to kill a n active task F1 > task terminate. The terminal runner tries to reuse terminals. Ensure that the reuse strategy makes sense. Play a little with task executed in the terminal. If you have ideas, please let me know. Executing them in the terminal opens new use cases.
Please also note that due to a problem in the terminal command quoting when executed in a shell doesn't work as expected. So a command like
"dir "folder with spaces""
is not correctly executed in a cmd.exe run in the terminal. See #19078 for details:Here is a sample tasks.json to start with:
The first task executes the tsc compiler in watch mode (assumes it is available globally). The second one executes the dir command using a special shell path for the terminal.
The text was updated successfully, but these errors were encountered: