Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"force TTY" command line option #1725

Closed
aishek opened this issue Mar 18, 2015 · 3 comments
Closed

"force TTY" command line option #1725

aishek opened this issue Mar 18, 2015 · 3 comments

Comments

@aishek
Copy link

aishek commented Mar 18, 2015

I'd like colorized output in Gitlab CI, but there "TTY only" color output in Rubocop. Maybe it'll be great to have "force TTY" command line option? What do you think?
@tknerr
Copy link

tknerr commented Apr 25, 2015

+1, or let's call it --force-color to be more aligned with the existing --no-color option

@tknerr
Copy link

tknerr commented Apr 25, 2015

...and --force-color should explicitly set Rainbow.enabled = true to override whatever rainbow.rb tries to auto-detect

@hesalx
Copy link

hesalx commented Jul 12, 2015

👍 Also using Gitlab CI and like colorful builds.

alexdowad added a commit to alexdowad/rubocop that referenced this issue Nov 2, 2015
@alexdowad
[Fix rubocop#1725] --color option forces color output (even when not …
ca314d6 
…printing to TTY)
@bbatsov bbatsov closed this as completed in a5ce6df Jan 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aishek @tknerr @hesalx