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 both in DDFileLogger and DDTTYLogger the '\n' character is added to each outputted string if the output does not end with the newline. This means that some custom formattings which would like to output multiple log messages in the same line are not possible.
Would it be possible to change both of those loggers not to add the newline character in case when the custom formatter is used. Then developers could provide their own formatters that would allow more control over the messages. Standard formatting would still add the newline character in the default case.
In case of DDFileLogger it just requires moving the line appending code from the log message to the default formatter. In case of DDTTYLogger it requires not adding the 5th element of the iovec struct array.
In case of ASL logger, the format is controlled by the asl api so no change is needed there.
The text was updated successfully, but these errors were encountered:
Currently both in DDFileLogger and DDTTYLogger the '\n' character is added to each outputted string if the output does not end with the newline. This means that some custom formattings which would like to output multiple log messages in the same line are not possible.
Would it be possible to change both of those loggers not to add the newline character in case when the custom formatter is used. Then developers could provide their own formatters that would allow more control over the messages. Standard formatting would still add the newline character in the default case.
In case of DDFileLogger it just requires moving the line appending code from the log message to the default formatter. In case of DDTTYLogger it requires not adding the 5th element of the iovec struct array.
In case of ASL logger, the format is controlled by the asl api so no change is needed there.
The text was updated successfully, but these errors were encountered: