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
thanks for reporting, The output in the colored.txt matches what i get from ipfs on a linux box. Could you try doing ipfs daemon --debug 2> output.txt and show the hexdump of that?
Since go-log is using a modified version of go-logging, maybe we can update the customized version with the changes in op/go-logging#110 once the PR for it is merged.
edit: it looks like the op/go-logging repo may not be active, so maybe waiting for the changes to be merged upstream isn't a good option.
Activity
whyrusleeping commentedon Aug 9, 2016
thanks for reporting, The output in the colored.txt matches what i get from ipfs on a linux box. Could you try doing
ipfs daemon --debug 2> output.txtand show the hexdump of that?mateon1 commentedon Aug 10, 2016
Apparently, the windows terminal only accepts ANSI escape codes with a specific flag enabled:
"The following terminal sequences are intercepted by the console host when written into the output stream if the ENABLE_VIRTUAL_TERMINAL_PROCESSING flag is set on the screen buffer handle using the SetConsoleMode flag."
(https://msdn.microsoft.com/en-us/library/windows/desktop/mt638032(v=vs.85).aspx)
Example usage in Go: https://github.com/jfrazelle/binctr/blob/master/vendor/github.com/docker/docker/pkg/term/term_windows.go
djdv commentedon Aug 15, 2016
Referencing old duplicate:
#2124
leerspace commentedon Nov 26, 2017
Since go-log is using a modified version of go-logging, maybe we can update the customized version with the changes in op/go-logging#110 once the PR for it is merged.
edit: it looks like the op/go-logging repo may not be active, so maybe waiting for the changes to be merged upstream isn't a good option.
djdv commentedon Jun 3, 2018
Resolved in: #5007