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 ANSI color codes present in source input are retained and printed in the output, even when redirecting to a file.
If a split is made within a color group, this may lead to an unescaped color code that causes all output to use that color.
In the log file being parsed the color code starts at the start of the second column and is terminated at the end of third:
By parsing the second column as a field we capture the start of the color code, but lose its termination. The stuck terminal color can be fixed by executing echo -e '\033[0m'.
I think it would probably be better to strip out color and other terminal escape codes from output.
The text was updated successfully, but these errors were encountered:
The vte crate (https://crates.io/crates/vte) might be useful here. Stripping the escape sequences before putting the string through parsers would probably be something to try.
Currently ANSI color codes present in source input are retained and printed in the output, even when redirecting to a file.
If a split is made within a color group, this may lead to an unescaped color code that causes all output to use that color.
In the log file being parsed the color code starts at the start of the second column and is terminated at the end of third:
By parsing the second column as a field we capture the start of the color code, but lose its termination. The stuck terminal color can be fixed by executing
echo -e '\033[0m'
.I think it would probably be better to strip out color and other terminal escape codes from output.
The text was updated successfully, but these errors were encountered: