Color fix needed?

[hemanth]

That's how it looks in my terminal, can read the text only after highlighting them!

The color of the text is gray!

[sindresorhus]

This is the grey color that is turned invisible: \x1B[90m

[sindresorhus]

@altercation @TrevorBramble bump. A lot of people are experiencing this bug...

[altercation]

What's generating this prompt?

(Yes, this is a significant issue. I want to test and repo)

[sindresorhus]

@altercation node-prompt, see here.

Also see the referenced issues above.

That text is invisible because the authors of Solarized Dark made the "bright black" color the same color as the background. Whoops. Also, for some reason, they made almost all of the "bright" colors not lighter, but darker than their "normal" counterparts.

[altercation]

So it's clear, this is not a "whoops" at all, but rather a very intentional and considered compromise based on the shitstorm of conflicting standards, expectations and legacy applications that is terminal emulation.

While a change is possible, and the information about which applications and programs suffer from issues like this is very helpful, it isn't going to happen immediately as any change is going to break the way something works.

This is probably the number one concern I have (the bright black issue) and I will only make a change once I'm certain it's the absolute best option.

[hellais]

I was also experiencing this issue with yeoman, not sure on which side the bug should be fixed, but the workaround I found is to use this my Xresources

#define hack_color #1c1c1c
*color8: hack_color

Changing the value of color8 to hack_color (it used to be set to !!base03 #002b36)

[satazor]

bump

[ghost]

I'm having the issue with the output from an ExpressJS application.

[cobyism]

Just ran into (what I believe is) this issue with yeoman. Here’s what the yeoman usage/help command looks like in iTerm2 with Solarized Dark:

…and with Solarized Light:

[cobyism]

Another example is the usage command of bower.

[mleveck]

What is the status of this? I just installed Yeoman 0.9.6 and large chunks of text are invisible in iTerm 2 with solarized dark. I'd let it go but:

1. My setup is far from uncommon. I'd say most OS X devs I know use iTerm2 and Solarized.
2. By definition Yeoman is a tool to make life easier, so I'd hope that fixing things like this might be a bit of a priority.

[ghost]

@mleveck You can look into the version in my pull request. Yeoman looks better with it...

[necolas]

Related problem in Mocha too - mochajs/mocha#802

[sindresorhus]

:/

[ghost]

Other themes give me the same problems such as Tomorrow Night Bright at https://github.com/chriskempson/tomorrow-theme. Really annoying.

[paulirish]

@altercation can you please look into this.
Seems bad to advocate that people to abandon solarized but... 6 months in, we're just about at that point.

[altercation]

@paulirish Sure. I'll take a look.

[necolas]

This problem is also affecting Express: expressjs/express#1700

Most of the popular front-end tools have been or are affected by this long-standing bug.

[sindresorhus]

This is just ridiculous...

[sheeit]

Here's a simple command to reproduce this:
if you have your terminal set up with the Solarized theme, just do

printf 'Normal text. \033[1;30mInvisible text\033[0m.\n'

The text "Invisible text" will not be visible.

[i-manolov]

i hope there are plans to fix this. I noticed the problem when trying to use mocha for the first time after changing to the solarized theme in iTerm2. Here is my work around for the moment:

• update black light to #0387ad or use Solarized Dark - Patched from https://github.com/mbadolato/iTerm2-Color-Schemes
• insert let g:solarized_termtrans = 1 in .vimrc as the vim theme uses the black light as a background color

[kyeotic]

@altercation Its been 4 years since you said you would take a look. Has there been any progress on this, or should we abandon solarized dark?

[icyflame]

hey @tyrsius, the possibility of this being fixed is remote. You should try using base16, I switched to that when I first encountered this issue and it's been pretty good. 😄

[jacoscaz]

@ivanmanolov90's solutions seems to works perfectly for me - at least with the tools I use.

[bobf]

I "fixed" this by setting iTerm2's black light colour to 0387ad (as suggested by @ivanmanolov90 ) and then using the following settings:

set background=dark
let g:solarized_termtrans = 1
colorscheme solarized

I know this won't work for everyone but if your setup is like mine then maybe it'll save you 15 minutes of frustration.

[icyflame]

I copied over the colors from gnome-terminal to iTerm2 and created a new color scheme. here. I tried using both base16 and base256 for iTerm2, but the first one simply didn't show some text and the second one had a weird problem where the difference between folders and files was very small (they were both white and the difference in font weight was not noticeable at all)

I have been using this for a couple days now, and it's not shown up any problems. I will report here if it does.

P.S the copying over process was pretty simple and you should absolutely do it if you have a preferred setup on a computer that works fine and want to emulate the setup elsewhere. (Not sure if this was already discussed here, I was unable to find it anywhere) 🤔

[laggardkernel]

I copied over the colors from gnome-terminal to iTerm2 and created a new color scheme. here.

I see. You're using the normal colors as the bright ones. I'm going to do the same. At least, the bright colors are not grey anymore.