-
-
Notifications
You must be signed in to change notification settings - Fork 17.1k
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
Color problems in terminal with certain themes #1700
Comments
+1, I usually switch to Solarized Light when I have an express app and would prefer Solarized finally fixing this, but an option to disable colors would still be helpful. |
you can use a non-"dev" format, the rest don't have colors, definitely a solarized thing, someone should just start a new 'official' fork haha, not sure, or maybe he can get a maintainer |
other themes also have this problem, but i know that you have always rejected the suggestion of making a change in your modules.
what does this mean exactly? |
maybe he meant express.logger('tiny') or express.logger('short') instead of app.use(express.logger('dev')). you can format the log string by your self and just the development settings would give the 'solarized thing'. You could build the logger dev format by your own without the color output too. just looking at logger.js middleware in connect |
I don't think we can go changing everything just because themes are incomplete, it's easy enough to use a theme that isn't as busted, or if that guy doesn't want to maintain solarized anymore I'm sure someone else would love to |
|
Change the *dev* logger to *short*, since log entries are not shown on a terminal with the solarized theme. expressjs/express#1700 (comment)
This thing again :)
Running
node app.js
in a terminal with the Solarized dark theme (and a few others), results in this unreadable output:Can I disable color output? Or might you be willing to use a gray that is visible in these popular themes, until they can be fixed?
The long-standing issue against Solarized: altercation/solarized#220
The text was updated successfully, but these errors were encountered: