build/win/use_ansi_codes.py - Issue 1194823004: clang/win: Make diagnostics colored if ansicon is around at runhooks time.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: build/win/use_ansi_codes.py

Issue 1194823004: clang/win: Make diagnostics colored if ansicon is around at runhooks time. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 5 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: build/win/use_ansi_codes.py

diff --git a/build/win/use_ansi_codes.py b/build/win/use_ansi_codes.py

new file mode 100644

index 0000000000000000000000000000000000000000..0cfdddba4a2b8e43252d74d83dccf8508f36ed94

--- /dev/null

+++ b/build/win/use_ansi_codes.py

@@ -0,0 +1,10 @@

+#!/usr/bin/env python

+# Use of this source code is governed by a BSD-style license that can be

+# found in the LICENSE file.

+"""Writes if the the terminal is likely to understand ANSI codes."""

hans 2015/06/19 21:53:59 ultra nit: Would "Prints whether" be better?

Nico 2015/06/19 22:02:49 Done.

+import os

+# Add more terminals here as needed.

+print 'ANSICON' in os.environ

« no previous file with comments | « build/config/compiler/BUILD.gn ('k') | no next file » | no next file with comments »