[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some serious issues with the new -O option

From: Tim Murphy
Subject: Re: Some serious issues with the new -O option
Date: Tue, 30 Apr 2013 12:22:56 +0100

I know this isn't going to go down all that well, but I really think the output should be annotated in such a way that colourisation could be applied to the log file after a build has already finished.

e..g you load a makefile into VIM - it can colourise it. Or a bit of C source code. Why not the log of a build you did yesteday? It's still very nice to be able to distinguish things by colour later on.



On 30 April 2013 11:16, Stefano Lattarini <address@hidden> wrote:
On 04/30/2013 12:01 PM, Tim Murphy wrote:
> What I mean is that:
> ./make -Otarget
> might be a good interactive default rather than -Omake.
I wasn't even aware of those differences; as of latest Git commit
'moved-to-git-46-g19a69ba', I don't see them documented in either
the help screen, the manpage, the texinfo manual, nor the NEWS file.

> Colouring is another issue which I would imagine could be done another way
> to let us have the best of both worlds.
That is not trivial to do I think.  For example, Automake-generated
testsuites check whether the stdout is a tty to decide whether or not
to automatically enable output colorization.  And testsuites produced by
Autotest do the same, AFAIK.  If the make connects the stdout of those
processes to non-tty files behind the scene, those checks are doomed to


You could help some brave and decent people to have access to uncensored news by making a donation at:


reply via email to

[Prev in Thread] Current Thread [Next in Thread]