about summary refs log tree commit diff
path: root/src/libstd
diff options
context:
space:
mode:
authorMark Rousskov <mark.simulacrum@gmail.com>2018-11-08 18:15:24 -0700
committerGitHub <noreply@github.com>2018-11-08 18:15:24 -0700
commitd293d1eea0b41e4ff65e8027e74eca9efd2dc7df (patch)
tree67c50601ac77481c7b2a8410c1c67f32fef2081f /src/libstd
parent667904f049febcb9df31e715144bf138dfe230f1 (diff)
parent255cc1aed33442567c29c95fa445a534575e925c (diff)
downloadrust-d293d1eea0b41e4ff65e8027e74eca9efd2dc7df.tar.gz
rust-d293d1eea0b41e4ff65e8027e74eca9efd2dc7df.zip
Rollup merge of #55788 - alexcrichton:wincolors, r=petrochenkov
rustc: Request ansi colors if stderr isn't a tty

Currently Cargo will always capture the output of rustc meaning that
rustc is never hooked up to a tty. To retain colors Cargo uses the
`fwdansi` crate to ensure that ansi color codes are translated to
windows terminal methods (and ansi codes otherwise just go their natural
route on Unix).

Cargo passes `--color always` to rustc to ensure that using a pipe
doesn't trick it into not emitting colors at all. It turns out, however,
that `--color always` ends up still accidentally using the native shell
api on native windows shells.

The fix here is to instead pass `AlwaysAnsi` to `termcolor` instead of
`Always`, ensuring that when `--color always` is passed to rustc and its
output isn't a terminal, we're always generating ansi colors regardless
of the platform.

Closes #55769
Diffstat (limited to 'src/libstd')
0 files changed, 0 insertions, 0 deletions