task runner output doesnt show color for gulp taks with --color switch arg

[mlakmal]

It is important to have color on the task output window to identify errors and success messagess in jasmine/karms test runner through gulp command. without this it is very hard to troubleshoot your unit test issues and identify issues in the code.

[bpasero]

The output control in VS code does not support colors at the moment.

[supersonicclay]

+1

[thojansen]

+1

[dzearing]

+1

[JonnyFox]

+1

[evisong]

+1

[hipstersmoothie]

+1

[vshabelnyk]

+1

[roryprimrose]

+1

[felixfbecker]

The VS Code integrated terminal already supports colors in the insider preview. Why not the tasks output / debugger console?

[JonnyFox]

+1

[nojvek]

I believe VSCode should have an option in tasks definition whether output should appear in terminal or just normal output window

[felixfbecker]

Actually, I just found out that the debug console supports colors too. It's only the tasks.

[madskristensen]

It would be very helpful if task console output is colorized in the Tasks window just like it is in the Terminal (ctrl+`) window.

[theDiverDK]

+1

[Van-Dame]

+1

[felixfbecker]

Guys there are now buttons for upvoting, please don't comment +1 anymore, it doesn't add any value to the discussion but creates a notification for everyone participating and clutters the thread

[nojvek]

If someone could give me guidance on where to look, I could send a PR for
this. I want this bad for a demo.

[jaime-olivares]

@nojvek, you just need to open a project and run the build (Ctrl-Shift-B or Ctrl-Command-Build). The 'Output' window will appear in the bottom of the window, showing the 'Tasks' output, similar to Visual Studio's 'Build' output. See sample screenshot here: https://code.visualstudio.com/images/tasks_problemmatcher.png
In that window, it is not possible to see colored text, as it is possible in a VS Code terminal window, which has coloring capability.
Without coloring capability, it is really hard to read the output of multiple tasks/tools, specially when trying to identify error messages.

[jaime-olivares]

Related stackoverflow post: http://stackoverflow.com/questions/30492083/can-i-get-colored-output-from-gulp-in-vscode-output-window

[triceam]

We just released a language extension that brings colorization to the Output panel. Basically, it is a language extension that adds the text/x-code-output mime type, which is used by the Output panel.

Get it here: https://marketplace.visualstudio.com/items?itemName=IBM.output-colorizer

Source here: https://github.com/IBM-Bluemix/vscode-log-output-colorizer Please help contribute! Bugs, feature requests, contributions all welcome.

[nojvek]

Why not just fix it in vscode? This seems like a core feature that should
be supported?

[triceam]

From what I have seen, all language colorization (syntax highlighting) is done with extensions, and it appears that the developer site encourages this approach. The extension could definitely be bundled with VSCode at build time with very little effort. I'd love to see it get in there.

IE: https://code.visualstudio.com/docs/customization/colorizer

[thomasboyt]

so, poking at the internals, I see that the output window is basically treated as another editor window, with a special MIME type, which is why @triceam was able to add syntax highlighting.

Very naive question here, but let's say that hypothetically the ANSI control codes for colorization weren't removed before the output is streamed to the terminal. Could a syntax highlighter be written that actually matched on these control codes to display colors in the output? It may be easier in the end to use a proper terminal emulator to display task output, but just a thought.

[fredrikaverpil]

Until the integrated terminal supports this, I'd like to run tasks in an external terminal window. Is this possible?
I can't find anything on that in the tasks runner docs.

[felixfbecker]

@fredrikaverpil set command to the command that starts processes in a new window on your OS, for example start on Windows, then pass in the actual command through args.

[fredrikaverpil]

Thanks! @felixfbecker

[bartlewis]

@fredrikaverpil I Have been trying to do the same. The lack of colors in output makes tasks quite crippled.

I was able to get this working on Mac, via the following. This opens Terminal, CDs into the current workspace, and then runs an NPM command (lint in this case).

{
  "version": "0.1.0",
  "command": "osascript",
  "suppressTaskName": true,
  "tasks": [
    {
      "taskName": "Lint",
      "args": ["-e", "tell application \"Terminal\" to do script \"cd ${workspaceRoot}; npm run lint\""]
    }
  ]
}

This is not ideal, as it spawns a new Terminal window each time. Ideally I would LOVE to direct this command to the internal terminal, or just have colors in output pane.

[MystK]

Is it possible to change these windows from a "Read Only Editor" type to a "Terminal" type so the ANSI control codes are supported?

[ChristianMoesl]

It is possible to run tasks in the integrated terminal by specifying "_runner": "terminal" in the tasks configuration.

[nojvek]

That would be pretty awesome. I'm using a plug in called run and save and if runs a defined command in existing terminal. So I think it should be doable. May be requires some work on the problem parsing.

…

On Sun, Mar 5, 2017 at 9:55 AM Christian Mösl ***@***.***> wrote: It is possible to run tasks in the integrated terminal by specifying "_runner": "terminal" in the tasks configuration. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#243 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVMNQXQMgcChGzUx0i25CAuf0zQ5Vks5rivb-gaJpZM4Gll6C> .

[osminogin]

@ChristianMoesl Great solution, thanks.

[geirsagberg]

I am amazed by VSCode and this community... I just now today caught myself thinking how cool it would be to have colored output from tasks, so I found this issue which is well over a year old, and @ChristianMoesl's answer is only from yesterday but solves the problem in a really neat way :)

[tsu1980]

Release note is here.

http://code.visualstudio.com/updates/v1_9?wt.mc_id=DX_878977#_task-execution-in-terminal

[nojvek]

`_runner` : why the underscore? Looks so ugly.

…

On Mon, Mar 6, 2017 at 11:36 PM, Tsuyoshi Sumiyoshi < ***@***.***> wrote: Release note is here. http://code.visualstudio.com/updates/v1_9?wt.mc_id=DX_ 878977#_task-execution-in-terminal — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#243 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVGIgR92kUal3_qaSYHfXxw-yUPRIks5rjQj5gaJpZM4Gll6C> .

[andyneff]

Thanks @ChristianMoesl.

It does "work", but you either have to select the window, press space, or else it doesn't clear the output every time the task is executed. It's nice to have color output (for GCC) again, but not as smooth as the default output behavior.

[nojvek]

_runner is still a hack. Color output should be supported in output window that understands ANSI codes. I find the problem matcher very helpful. May be VSCode shouldn't strip out ANSI codes, but parse them and send a tokenized output to watcher window rather than raw text.

[Ciantic]

Problem with running in Terminal is that it breaks the window system, this must be done on output view.

Run on Save fork that runs in terminal for instance always opens the terminal when it runs. This has annoying side effect that the in Zen mode the terminal pops up from nowhere when I save.

[lfaoro]

Use "runner": "terminal" directive.

{
  "version": "0.1.0",
  "runner": "terminal",

  "tasks": [
    {
      "taskName": "Run Go Code",
      "isShellCommand": true,
      "isBuildCommand": true,
      "showOutput": "always",
      "command": "go",
      "args": [
        "run", "*.go"
      ]
    }
   ]
}

[mscottx88]

If this is still an issue for folks, I found a workaround. Set your settings in VS Code to use the short name variant of the path to Git Bash.

"terminal.integrated.shell.windows": "C:/Progra~1/Git/bin/bash.exe"

[joggienl]

I'm curious, what is the current status of this issue and what will be done to solve it? There are some workarounds etc. in this thread, but the main question is, can we get coloured output in the output panel as well? I think this mainly goes for commands that "normally" go through the terminal but could also go through the output window.

For instance, if I run my yarn or npm commands to the output window in stead of the terminal, a line with green color is shown as following:

[32;1mindex.js

You can allow output to the output pannel through setting runInTerminal to false (for npm or yarn or even both if you like).

I have looked at the IBM plugin, the Output Colorizer. It looks nice but I think it does not do what we expect for terminal like commands. The yarn/npm commands (maybe by a package like chalk even!) are intentionally coloured. The Output Colorizer just makes assumptions on colours. Thats not the same imo.

[daldr-ntml]

I have a build task that builds a C++ project using C++. I would like to color the errors reported by gcc.

I have installed the Colorizer plugin (mentioned above) and that plugin does indeed color text in the Output window. However, my build task sends its output to the Terminal window and Colorizer seems to have no effect on Terminal.

Not sure what is going on here. Has the behavior of VS Code changed this year such that task output is now sent to Terminal instead of Output?

Can Colorizer act on Terminal?

Or, is there another way of colorizing the output of Terminal?

[dbaeumer]

Actually this got implemented by executing tasks in the terminal with task v2.0.0. I will close the issue since the original description is resolved. Please open separate issue if you think something is not working correctly in terms of coloring in the terminal.

[nojvek]

@dbaeumer do tasks in terminal support problemMatcher and isBackground ?

[dbaeumer]

Yes, they do.