Files
mercury/tests/invalid_onlydepend
Zoltan Somogyi 3452cbb107 Implement the MERCURY_ENABLE_COLOR envvar.
compiler/mercury_compile_main.m:
    If this new environment variable is set to always/never/1/0,
    then enable or disable the use of color as directed. Do this regardless
    of the setting of the NO_COLOR environment variable, since NO_COLOR
    is a general setting while MERCURY_ENABLE_COLOR is a specific setting.
    NO_COLOR is still consulted if MERCURY_ENABLE_COLOR is either not set,
    or is set to a value we don't recognize.

compiler/globals.m:
    Now that color diagnostics can be disabled using this new purpose-specific
    envvar, stop taking an "" or "none" value of the MERCURY_COLOR_SCHEME
    envvar as a request to disable colors in diagnostics.

compiler/options.m:
    Shorten the name of the --enable-color-diagnostics option to just
    --color-diagnostics.

compiler/handle_options.m:
    Conform to the changes above.

tools/bootcheck:
    Set MERCURY_ENABLE_COLOR to "always". Delete the unset of NO_COLOR,
    since it should not be needed.

tests/invalid/Mmakefile:
tests/invalid_make_int/Mmakefile:
tests/invalid_nodepend/Mmakefile:
tests/invalid_onlydepend/Mmakefile:
tests/invalid_purity/Mmakefile:
tests/invalid_submodules/Mmakefile:
tests/recompilation/Mmakefile:
tests/warnings/Mmakefile:
    Update the references to ---enable-color-diagnostics. Bootchecks would
    work even if we deleted them, but keeping them slightly simplifies
    running the tests outside of bootcheck.
2024-06-15 08:47:40 +10:00
..