Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
B
benchmark
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • benchmark
  • Repository

Switch branch/tag
  • benchmark
  • src
  • commandlineflags.h
Find file
BlameHistoryPermalink
  • Nicholas Hutchinson's avatar
    Auto-detect whether Benchmark should produce colorized output (#126) · 917b86e6
    Nicholas Hutchinson authored Sep 15, 2016
    * Auto-detect whether to produce colorized output
    
    Rename --color_print to --benchmark_color for consistency with the other
    flags (and Google Test). Old flag name is kept around for compatibility.
    
    The --benchmark_color/--color_print flag takes a third option, "auto",
    which is the new default. In this mode, we attempt to auto-detect
    whether to produce colorized output. (The logic for deciding whether to
    use colorized output was lifted from GTest:
    <https://github.com/google/googletest/blob/master/googletest/src/gtest.cc#L2925>.)
    
    * Update CONTRIBUTORS, AUTHORS
    917b86e6
commandlineflags.h 3.13 KB
EditWeb IDE
×

Replace commandlineflags.h

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.