4 ms·
oh please no. please don’t just simply set all stderr to red - it doesn’t help at all, and makes reading multi-line things near impossible (there is a reason wh
by foxhill 8y ago
oh please no. please don’t just simply set all stderr to red - it doesn’t help at all, and makes reading multi-line things near impossible (there is a reason why most image/video codecs use 1/2 as many bits to encode red colour data).
besides, what happens to colourisation of output from stderr when a process gives useful color output?
UX is not really my remit (you could maybe guess :) but i’d greatly prefer bold, or stdout as grey, stderr as white - only if no colour control codes are present in the written message.
still, kudos for monkey patching libc :)
- extrapickles 8y agoThat would be much better for those of us who are red/gred colorblind if it was just bolded white. It can be quite hard to read deep red text on a black background. You don’t always have enough access to systems to change the default coloring to prevent this.
- basicer 8y agoYou can actually set an environmental variable with any color code you want: STDERRED_ESC_CODE. As for color codes in stderr, they work in most cases. If all the color codes are in a single write(), it will more or less be unaffected by the extra red and reset color codes that get stuck on either end.
- mixmastamyk 8y agoAnsi red is not great for the reasons you state, but italic, reversed, underlines might work too.