On Wed, Oct 25, 2017 at 4:07 PM, Mathieu Lirzin <m...@gnu.org> wrote: > Hello, > > Mike Mestnik <cheako+gnu_...@mikemestnik.net> writes: > >> Somethings I'v spotted that are driving me nuts. >> http://git.savannah.gnu.org/cgit/automake.git/tree/lib/tap-driver.sh#n100 >> Clearly indicates that "--color-tests=yes" is the only way to enable >> color, there is no auto-detecting a PTY or any support for the >> documented "--color-tests=always" > > The detection is done in the generated Makefile which invokes > tap-driver.sh with the appropriate command line arguments. Duplicating > detection inside the test driver would make sense only in the context of > invoking it interactively. > This is something important for me to be aware of, as I am planing on making changes I'll need to understand the whole system. I'll read check.am now.
Thanks. > Do you have a use case where we would want to invoke tap-driver.sh > outside of the 'make check' context? > I just needed to know why the script and the documentation were mismatched. > Thanks. > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
