-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
--no-colors for run command #1067
Closed
ghost opened this issue
May 18, 2014
· 2 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed
--no-colors for run command #1067
ghost opened this issue
May 18, 2014
· 2 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Labels
Comments
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 5, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 7, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 9, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 9, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 20, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Jan 20, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
@dignifiedquire I believe that we can close this issue :) |
Yes :) |
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 13, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 13, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 21, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 21, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 22, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 22, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 22, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
budde377
added a commit
to budde377/karma
that referenced
this issue
Feb 22, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
danielcompton
pushed a commit
to danielcompton/karma
that referenced
this issue
Jun 20, 2016
Add colors and log-level arguments to run argument. Refactor log-setup functions for server and init. Correct bug in server where log-level was ignored before `parseConfig` Closing karma-runner#1067
danielcompton
pushed a commit
to danielcompton/karma
that referenced
this issue
Jun 20, 2016
Delay the decision on color/no-color reporter to write. This is done by letting the individual adapter decide the color and providing a default color to the base adapter. Closing karma-runner#1067
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to do this:
And it keeps displaying ANSI colors. I'm trying to pipe the output from the
run
command into Emacs and other text editors and I really really don't want to have to add extra code that strips out the ANSI colors when therun
command really should be accepting the--no-colors
argument just like thestart
command does.I've tried setting the option in my config with
color:false
but that apparently only applies to the first running instance of karma, not to any subsequent calls to the karma server.The text was updated successfully, but these errors were encountered: