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
I am trying to colorize the output of some GitLab traces and it has coloring support. This coloring is done through the use of ANSI escape sequences, but I'm not able to convert them directly to html using this package.
The issue lies with the Select Graphic Rendition reset, which is rendered by GitLab with the stream "ESC [0;m". According to Wikipedia those commands do not contain the semicolon, but there are other commands, such as the foreground color set that in fact include the semicolon (such as ESC [38;5;128m).
I suggest to check if the character next to the semicolon is a parameter (which would be numeric) or if it is the terminator, instead of assuming that it is a number on the first place.
I'm willing to do the work, but if possible, it would be nice if this patch would be merged in the code.
Best regards!
The text was updated successfully, but these errors were encountered:
$ cargo r -qthread 'main' panicked at src/main.rs:2:56:called `Result::unwrap()` on an `Err` value: ParseInt(ParseIntError { kind: Empty })note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
And the same thing works fine in a terminal
I'm willing to do the work, but if possible, it would be nice if this patch would be merged in the code.
I'd be willing to review a PR for it if that's fine with @Aloso
I am trying to colorize the output of some GitLab traces and it has coloring support. This coloring is done through the use of ANSI escape sequences, but I'm not able to convert them directly to html using this package.
The issue lies with the Select Graphic Rendition reset, which is rendered by GitLab with the stream "ESC [0;m". According to Wikipedia those commands do not contain the semicolon, but there are other commands, such as the foreground color set that in fact include the semicolon (such as ESC [38;5;128m).
I suggest to check if the character next to the semicolon is a parameter (which would be numeric) or if it is the terminator, instead of assuming that it is a number on the first place.
I'm willing to do the work, but if possible, it would be nice if this patch would be merged in the code.
Best regards!
The text was updated successfully, but these errors were encountered: