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
Make stdout text yellow if the the string starts with a user defined set of strings, like "warn" or "err". (we don't actually need regexps to avoid teh overhead)
We could make it a bit smart to avoid the initial chars on the line that are not actual chars (including stars, spaces, tabs, etc).
I am not sure if this would work to be honest due to buffering... I would like to hear your opinion on this.
Thanks
The text was updated successfully, but these errors were encountered:
I am curious in which direction this could go because now I rely complex iTerm regexes for coloring the output. If stderred could strd doing that I port them and rely less on iTerm (which is MacOS only)
This would also allow color escape codes to only be emitted on new lines instead of every time printf is called. Many programs print as they go, which is fine until the program changes the color, does some work, and then tries to print some more stuff. The end result is the color gets changed back by stderred and the application's color is not seen.
For example the backward.cpp library pretty prints backtraces with color, but doesn't work with stderred without modifying the source code because of the previously described behavior.
Amazing project. Just love it.
Here a suggestion for a new feature:
Make stdout text yellow if the the string starts with a user defined set of strings, like "warn" or "err". (we don't actually need regexps to avoid teh overhead)
We could make it a bit smart to avoid the initial chars on the line that are not actual chars (including stars, spaces, tabs, etc).
I am not sure if this would work to be honest due to buffering... I would like to hear your opinion on this.
Thanks
The text was updated successfully, but these errors were encountered: