6 ms·
Nope - it's pretty unreadable in iterm2 for me - http://i.imgur.com/bKQwIdJ.jpg http://i.imgur.com/bKQwIdJ.jpg Shame, the idea is pretty neat. If you can solve
by mcjiggerlog 9y ago
Nope - it's pretty unreadable in iterm2 for me - http://i.imgur.com/bKQwIdJ.jpg http://i.imgur.com/bKQwIdJ.jpg
Shame, the idea is pretty neat. If you can solve that issue, OP, I'd love to give it a proper try.
- okdana 9y agoThe question i have is why do users configure their terminals to use colours that are unreadable to them? If your blue doesn't look right on your dark background, why are you using that blue? If your yellow doesn't look right on your light background, why are you using that yellow? I mean i get how this can be a problem with hard-coded arbitrary values — you can't ever guarantee that e.g. #ff6600 will go with anyone's particular colour scheme. But these 8 or 16 standard colours are not hard-coded, they're configurable in every terminal i've ever used, including Windows's shitty command prompt. They can and should be set to a value that's appropriate for your background and text colours. Maybe this is more a fault of the terminal/theme developers for providing unusable defaults. idk.
- toast0 9y agoPersonally, I didn't want to invest the time in color schemes when I was trying out a new terminal... however many years later, I like the terminal, but never cared enough. Most of the colors that show up are fine I guess (except the helpful serial over lan controller that manages to set the background and the foreground to the same color :( )
- mcjiggerlog 9y agoBecause those colours never show up. I've never had a problem with readability till now.