Terminal actions are not available for CustomExecution task output.

[elmar-peise]

A lot of useful terminal actions are guarded by the terminalProcessSupported context key. However, even without process support, the vscode.CustomExecution mechanism used in the tasks API will stream output to terminal panels.

This means that in environment without process support, many features are not available for task output, notably including "Terminal: Focus Find" (Ctrl+F).

Can we change the preconditions/when clauses for these actions to also enable such features for task output without process support? I see two options:

1. Remove the restrictions entirely, or
2. Replace terminalProcessSupported with something like terminalProcessSuppported || hasCustomExecution, where hasCustomExecution would be set when a task with a vscode.CustomExecution starts.

Please let me know if either of these make sense and if you would be open to accept a corresponding pull request.

[Tyriar]

Sorry about the delay.

The restrictions are added so that we can simplify the UI such that irrelevant commands are hidden from the command palette when not needed. I think option 2 is good but maybe instead of using a hasCustomExecution context key we should have a hasHadTerminal one or something, which would switch on when the first terminal is created. Note that this doesn't just impact custom execution tasks but also the Pseudoterminal API which works in web too.

[Tyriar]

@meganrogge we should hook these up to the new context key you made.

[alexr00]

Verified by starting a custom execution task then making sure that the Terminal: Focus Find command works.