|Subject:||Re: Some serious issues with the new -O option|
|Date:||Tue, 30 Apr 2013 12:22:56 +0100|
On 04/30/2013 12:01 PM, Tim Murphy wrote:I wasn't even aware of those differences; as of latest Git commit
> What I mean is that:
> ./make -Otarget
> might be a good interactive default rather than -Omake.
'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.
That is not trivial to do I think. For example, Automake-generated
> Colouring is another issue which I would imagine could be done another way
> to let us have the best of both worlds.
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
|[Prev in Thread]||Current Thread||[Next in Thread]|