Chronicles is not disabling its colored output when piped to another program. #1
Comments
Open
zah
added a commit
that referenced
this issue
Nov 3, 2021
* Log levels can be specified per sink * The log format can now be specified at run-time * The usage of colors can be controlled at run-time (fixes #1) * When a log statements logs an exception, the stack trace of the exception will be printed in a more readable form (on multiple indented lines with one call stack entry per line). The feature is enabled only in debug builds or when explicitly requested with `-d:chronicles_stack_traces:on`. * The printing of complex objects in formats `textlines` and `textblocks` has been improved. Type-specific overrides such as `chronicles.formatIt` will now affect the formatting of the object fields. * Most log statements won't perform any allocations. The details depend on the logged object types. * The type of line ending characters used by Chronicles can be controlled with `-d:chronicles_line_endings`. Supported values are 'windows', 'posix` and 'platform'.
zah
added a commit
that referenced
this issue
Nov 3, 2021
* Log levels can be specified per sink. * The log format can now be specified at run-time. * The usage of colors can be controlled at run-time (fixes #1). * Use UTC timestamps by default. * Added a new 'LocalRfcTime' timestamp scheme to preserve the old behavior of logging local time. * When a log statements logs an exception, the stack trace of the exception will be printed in a more readable form (on multiple indented lines with one call stack entry per line). The feature is enabled only in debug builds or when explicitly requested with `-d:chronicles_stack_traces:on`. * The printing of complex objects in formats `textlines` and `textblocks` has been improved. Type-specific overrides such as `chronicles.formatIt` will now affect the formatting of the object fields. * Most log statements won't perform any allocations. The details depend on the logged object types. * The type of line ending characters used by Chronicles can be controlled with `-d:chronicles_line_endings`. Supported values are 'windows', 'posix` and 'platform'.
zah
added a commit
that referenced
this issue
Nov 4, 2021
* Log levels can be specified per sink. * The log format can now be specified at run-time. * The usage of colors can be controlled at run-time (fixes #1). * Use UTC timestamps by default. * Added a new 'LocalRfcTime' timestamp scheme to preserve the old behavior of logging local time. * When a log statements logs an exception, the stack trace of the exception will be printed in a more readable form (on multiple indented lines with one call stack entry per line). The feature is enabled only in debug builds or when explicitly requested with `-d:chronicles_stack_traces:on`. * The printing of complex objects in formats `textlines` and `textblocks` has been improved. Type-specific overrides such as `chronicles.formatIt` will now affect the formatting of the object fields. * Most log statements won't perform any allocations. The details depend on the logged object types. * The type of line ending characters used by Chronicles can be controlled with `-d:chronicles_line_endings`. Supported values are 'windows', 'posix` and 'platform'. * Some unprintable characters are now displayed as hex value * The 'dynamic' sinks are now renamed to 'callback' to free the 'dynamic' term for other uses. * Updated the list of TODO items
zah
added a commit
that referenced
this issue
Nov 4, 2021
* Log levels can be specified per sink. * The log format can now be specified at run-time. * The usage of colors can be controlled at run-time (fixes #1). * Use UTC timestamps by default. * Added a new 'LocalRfcTime' timestamp scheme to preserve the old behavior of logging local time. * When a log statements logs an exception, the stack trace of the exception will be printed in a more readable form (on multiple indented lines with one call stack entry per line). The feature is enabled only in debug builds or when explicitly requested with `-d:chronicles_stack_traces:on`. * The printing of complex objects in formats `textlines` and `textblocks` has been improved. Type-specific overrides such as `chronicles.formatIt` will now affect the formatting of the object fields. * Most log statements won't perform any allocations. The details depend on the logged object types. * The type of line ending characters used by Chronicles can be controlled with `-d:chronicles_line_endings`. Supported values are 'windows', 'posix` and 'platform'. * Some unprintable characters are now displayed as hex value * Rename the automatically inserted 'file' property to 'src' in order to avoid clashes with user variables (i.e. 'file' is a common variable name). * The 'dynamic' sinks are now renamed to 'callback' to free the 'dynamic' term for other uses. * Updated the list of TODO items
zah
added a commit
that referenced
this issue
Nov 4, 2021
* Log levels can be specified per sink. * The log format can now be specified at run-time. * The usage of colors can be controlled at run-time (fixes #1). * Use UTC timestamps by default. * Added a new 'LocalRfcTime' timestamp scheme to preserve the old behavior of logging local time. * When a log statements logs an exception, the stack trace of the exception will be printed in a more readable form (on multiple indented lines with one call stack entry per line). The feature is enabled only in debug builds or when explicitly requested with `-d:chronicles_stack_traces:on`. * The printing of complex objects in formats `textlines` and `textblocks` has been improved. Type-specific overrides such as `chronicles.formatIt` will now affect the formatting of the object fields. * Most log statements won't perform any allocations. The details depend on the logged object types. * The type of line ending characters used by Chronicles can be controlled with `-d:chronicles_line_endings`. Supported values are 'windows', 'posix` and 'platform'. * Some unprintable characters are now displayed as hex value * Rename the automatically inserted 'file' property to 'src' in order to avoid clashes with user variables (i.e. 'file' is a common variable name). * The 'dynamic' sinks are now renamed to 'callback' to free the 'dynamic' term for other uses. * Updated the list of TODO items
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: