Improve debugging

[marcosh]

Is your feature request related to a problem? Please describe.
I'm trying to setup tricorder with a complex project, I'm failing because I get weird compilation errors.
In particular it's hard to debug because I don't know precisely which command tricorder is calling, so I'm not able to reproduce the issue on a lower level

Describe the solution you'd like
I think a good solution would be to log in the tricorder log output every call to an external tool, might it be cabal, stack, hpack or ghci and, optionally, every output they provide

Describe alternatives you've considered
Maybe a separate log file could be used to log output from external tools.
Then the log output could be filtered with some verbosity flag

[Gipphe]

Technically, Tricorder already has a LOG/LOGGING/DEBUG env var flag that can be set to increase logging verbosity, but it is a bit underutilized at the moment, and it's also sort of broken for debug logs, for reasons we haven't had the time to get into yet.

I like your suggestion. Makes sense to log external program calls for debugging purposes, but it might make sense to keep these behind a verbosity flag, like LOG=Debug/LOGGING=Debug/DEBUG=1.

[marcosh]

I like your suggestion. Makes sense to log external program calls for debugging purposes, but it might make sense to keep these behind a verbosity flag, like LOG=Debug/LOGGING=Debug/DEBUG=1.

yes, I agree, such information should be shown only as debugging information