-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Set output line colors by rules #184
Comments
Thank you very much for your suggestion. BTW, have you ever tried this extension MetaOutput? |
Thanks for the suggestion, I didn't know MetaOutput yet - it seems to be overkill for my purposes (just colorizing the output, but leaving the order/display of messages as-is). I'll check simpler extensions for that. Again, thanks :-) |
I am currently using this. I've tried quite a few output colorizers, and this one works the best. |
I will investigate whether it is possible to change the styles for things in the Output window pane. |
Hi, Please download and test the recently released beta, which has implemented syntax highlight style customization in the output window. If you have installed the VSColorOutput extension or its 64bit counterpart, you can now use Codist to customize the style of the parsed output. As for the goal of "reduce extension count", I still need time. At least, we can customize the style of the output window now. |
Well, I reviewed this issue and the recent progress of Codist 8.0 (#334), which allows the user to customize their own Regular Expression based rules and syntax highlight classification types. It is not too far for me to implement this feature. |
Hi, there's a new beta version which enables you to customize the highlight of the Output window. This function is in its early stage. Please download it from the 8.0 Beta page above, and be sure to read the Wiki page. |
There are other extensions that can colorize the (build-) output by rules (e.g. lines containing "error" = red, lines containing "warn" = orange, ...) - but it would be cool to have this in codist, as well (to reduce extension count and because it nicely adds to the existing codist coloring/highlighting features)
The text was updated successfully, but these errors were encountered: