Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gcc tends to output in colour by default these days, but only if it's running in a terminal. It's actually quite useful when trying to make sense a long pile of compiler spew. Of course, muddle confounds this by capturing the output.
Plan A: Update the
Makefile.muddle
of every last package to set-fdiagnostics-color=always
. Hahahahahahaha.Plan B: Teach muddle to colourise the output itself, along similar lines to what gcc and friends do.
This is Plan B. I've been using it for a couple of weeks now and it's pretty solid so far. It's intended to be a safe drop-in: if you don't have the python colorama package installed, muddle continues to operate just how it used to, and you get a note telling you what you have to do to install colorama.
As a bonus feature, you can set an environment variable which will chuck HTML spans around the output instead, ready for use in a CI system with suitable CSS.