You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, paperless-cli seems to unconditionally use colors for its output which makes the output unreadable in my setup (I am using the solarized theme):
While handling such edge cases may be out of scope for this tool, it would be nice to add an option to use uncolored output so the tool can be used in such environments. Also, I noticed that colors are used even if the output is redirected to a file etc. I would suggest only enabling output colors by default if stdout goes to a terminal, as is done by many other tools and probably the best practice when offering colored output.
The text was updated successfully, but these errors were encountered:
Hi.
I'm using a 3rd-party library to handle logging and its colored output formatting.
I want to transition to the new Go structured logging feature, but this library doesn't yet fully support it. So I'm awaiting pterm/pterm#603 to get resolved first, otherwise I might end up doing the same effort twice after switching to the new logging stack.
Currently, paperless-cli seems to unconditionally use colors for its output which makes the output unreadable in my setup (I am using the solarized theme):
While handling such edge cases may be out of scope for this tool, it would be nice to add an option to use uncolored output so the tool can be used in such environments. Also, I noticed that colors are used even if the output is redirected to a file etc. I would suggest only enabling output colors by default if stdout goes to a terminal, as is done by many other tools and probably the best practice when offering colored output.
The text was updated successfully, but these errors were encountered: