how to enable terminal color output?

[y9c]

the output

expected result

[skywind3000]

ANSI color escape code is not supported, and I don't have any plan for that. You should disable gcc color output, errors will be highlighted by quickfix window itself.

[noboruma]

Looks like this plugin works fine: https://github.com/powerman/vim-plugin-AnsiEsc

[dakeryas]

Running AnsiEsc in the quickfix window opened by an AsyncRun command does work, but how does one combine both in a single command?

I am running two commands separately at the moment:

:AsyncRun clang++ -fdiagnostics-color=always  -c % -o /dev/null
:AnsiEsc

I have tried piping the commands, e.g.

:AsyncRun clang++ -fdiagnostics-color=always  -c % -o /dev/null | AnsiEsc

to no avail.

[skywind3000]

-post=xxx

[oliverdain]

As an alternative, it'd be nice if we could choose environment variables that get set for any :AsyncRun call. In particular, in my case if I run :AsyncRun echo $TERM I get:

|| [echo $TERM]
|| xterm-256color
|| [Finished in 0 seconds]

so my compilers, etc. think the quickfix window supports colors and that breaks errorfmt. I can update which commands I run to turn off colors for each of our build tools (linters, compilers, code generators, etc.) but it'd be easier if we could just globally set the terminal config so it tells everything that colors aren't going to work.

Is that possible?

[skywind3000]

use this:

:AsyncRun -mode=term -pos=TAB  xxx

[oliverdain]

use this:

:AsyncRun -mode=term -pos=TAB  xxx

@skywind3000 thanks for the suggestion. When I do that it doesn't populate the quickfix window so I can't jump to errors. The reason I want to eliminator the color output is so my errorfmt works and I can quickly handle compiler and linter errors. Is there a way to use -mode=term and still have quickfix like functionality?