Re: make compilation not so gray

On 05/26/2018 03:57 AM, Craig Small wrote: > > > On Fri, 25 May 2018, 22:21 Adam Borowski, > wrote: > > But, nice folks who make gcc have introduced an option which helps here: > -fdiagnostics-color.  It's very nice even for terse logs (such as the >

Re: make compilation not so gray

On 27/05/18 10:21, Adam Borowski wrote: [Warning: a long-winded rant about terminals. You should have known better than to get me onto this particular topic.] I am pleased. It is working out very well for me :-) On Sat, May 26, 2018 at 12:57:39PM +1200, Ben Caradoc-Davies wrote: Exhibit

Re: make compilation not so gray

[Warning: a long-winded rant about terminals. You should have known better than to get me onto this particular topic.] On Sat, May 26, 2018 at 12:57:39PM +1200, Ben Caradoc-Davies wrote: > On 26/05/18 12:28, Ben Caradoc-Davies wrote: > > On 26/05/18 00:21, Adam Borowski wrote: > > > It might be

Re: make compilation not so gray

Ben Caradoc-Davies wrote: > Exhibit A: dpkg-buildpackage (attached). This was just the one in front > of me. FWIW if I have chosen to configure a terminal with a light coloured background, I also configure the standard ANSI colours so that there will be sufficient contrast to read them against

Re: make compilation not so gray

On Fri, 25 May 2018, 22:21 Adam Borowski, wrote: > But, nice folks who make gcc have introduced an option which helps here: > -fdiagnostics-color. It's very nice even for terse logs (such as the > kernel), but for our use case it gives a ridiculously good improvement: >

Re: make compilation not so gray

On 26/05/18 00:21, Adam Borowski wrote: It might be good to pipe output through ansi2txt Thank you so much for alerting me to ansi2txt. Given the miserable failure of some command line tool authors to contemplate terminal background colours other than black, I have had to endure all manner

Re: make compilation not so gray

On 26/05/18 12:28, Ben Caradoc-Davies wrote: On 26/05/18 00:21, Adam Borowski wrote: It might be good to pipe output through ansi2txt Thank you so much for alerting me to ansi2txt. Given the miserable failure of some command line tool authors to contemplate terminal background colours other

Re: make compilation not so gray

Guus Sliepen - 25.05.18, 21:46: > On Fri, May 25, 2018 at 02:21:34PM +0200, Adam Borowski wrote: > > I propose to add a new flag: DEB_BUILD_OPTIONS=color. […] > That would be very helpful. > > Even more helpful would be to NOT display anything irrelevant. When a > package fails to build, I am

Re: make compilation not so gray

Guus Sliepen writes: > Even more helpful would be to NOT display anything irrelevant. When a > package fails to build, I am generally only interested in the error > message, not everything that led up to it, because up until the error > message everything went fine, and the

Re: make compilation not so gray

On Fri, May 25, 2018 at 02:21:34PM +0200, Adam Borowski wrote: > I heard a rumour some of us might need to read a package build log from time > to time. Those have grown enormously wordy during past decades: we include > all kinds of doodads about the build environment, and the compilation

make compilation not so gray

Hi! I heard a rumour some of us might need to read a package build log from time to time. Those have grown enormously wordy during past decades: we include all kinds of doodads about the build environment, and the compilation itself has all verbosity options turned on. This makes searching for