Using "outputTo" with "terminal" to open new terminal instance rather than using most recent

[yoiang]

Hello y'all!
I apologize for all the issue posts but I'm excited to wrap this extension into my daily usage! Thanks again for the effort you've put into it 😄

This request is to (configurable-y?) have outputTo with terminal use a new Terminal window for each Task run. This is most important because any task that is long or even on-going until explicitly terminated isn't recognized, and pressing "Run Task" on other task while this long-running Terminal tab is selected will result in the task command being sent to the application that is running rather than being properly executed.

This is the MVP of the request, further awesomeness would be things like:

• simple process status monitoring within the tasks window, something like a process indicator while running and "Run Task" being swapped out for "Stop Task", however this doesn't work when one wants to purposefully spawn multiple instances of the same task at once. Task Explorer does something like this
• reuse of the same window for the same task if the previous run has finished, new windows being opened if the previous run is still going
• auto-exiting of the Terminal process like many other runnings who keep the window open with "Process finished, press any key to close..." kinda prompt

[beholdr]

+1. For long tasks (like dev server) I need to use output to a terminal because with default output I can't stop process when I need it. And with output to a terminal it is very often when task runs in the wrong terminal. But to have an ability to stop a running task would be event better.

[321gocheck]

+1

[pd93]

There are multiple suggestions in the OP beyond the scope of the PR that closed this issue. If these are still feature requests. Please open new issues for them so they can be tracked separately.