As I'm reporting a few Issues with agebox today, I find myself using screenshots rather than simply capturing the text output of the tool. This is because:
- the "normal" user interaction, at the shell, is via colorized logs
- diverting colorized output into a file, for copy'n'pasting here in github, includes color-related escape codes (yes, the're removable with
sed/etc, but still ...)
- using the
--no-color output option does more than simply stripping the color-related escape codes from the log output - it changes the logging format such that it's not representative of the "normal" user experience any longer.
Here's a screenshot :-)
This is somewhat annoying for filing github Issues.
But more than that, it stops a color-intolerant user (or build system, or script, etc etc) from being able to access the "normal" format of the logs.
Request: make --no-color do only the single job of not outputting color-related escape codes. Leave the log format modifications to other flags.
As I'm reporting a few Issues with agebox today, I find myself using screenshots rather than simply capturing the text output of the tool. This is because:
sed/etc, but still ...)--no-coloroutput option does more than simply stripping the color-related escape codes from the log output - it changes the logging format such that it's not representative of the "normal" user experience any longer.Here's a screenshot :-)
This is somewhat annoying for filing github Issues.
But more than that, it stops a color-intolerant user (or build system, or script, etc etc) from being able to access the "normal" format of the logs.
Request: make
--no-colordo only the single job of not outputting color-related escape codes. Leave the log format modifications to other flags.