Closed wgj closed 7 years ago
@dbaeumer is this as designed under tasks v2?
@Tyriar yes and no. I simply couldn't find a way to print something to the terminal. The command itself is started with the runTerminal and therefore it is not printed. Would it be possible for the terminal to echon that if I asked it to do so.
@dbaeumer it's not possible now, would this make sense as a member on IShellLaunchConfig
that is parsed and written to the terminal front end before the process starts (including escape sequences)?
Yes, would make perfect sense on IShellLaunchConfig
I added IShellLaunchConfig.initialText
which you can set with escape sequences so you can style if you wish. Tested by setting: _shellLaunchConfig.initialText = 'abc foo \x1b[33mbar\x1b[0m adsa';
, here's the result:
Note my prompt has an empty line at the start so only the first line was added. See comment in https://github.com/Microsoft/vscode/commit/848157095a77ac6a5baac0d0aa6ffecf4f65920a for more usage details.
Passing to you @dbaeumer :smiley:
Hey everyone,
I think we may have missed the usecase on this one. I have many tasks defined in tasks.json, and when I run them, I'd like visual feedback on what command, with which parameters, was ran.
8481570 appears to prepend a hardcoded string to every shell instance, without a reference to a given task (as in tasks.command
and tasks.args
from tasks.json)
@wgi this needs adoption in the task framework this is why I opened #22655
Alright :)
I don't understand the process, and I had a mild panic when I saw this issue had been closed. Thank you.
When using
echoCommand
in tasks.json, the command isn't echoed in the Integrated Terminal.Steps to Reproduce:
echoCommand
.