-
Notifications
You must be signed in to change notification settings - Fork 301
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
Conflicts with Output Colorizer extension #59
Comments
Hi @adenflorian , thanks for reporting this issue! I have reported this to VS Code team for help. |
The IBM OutputColorizer extension is extremely useful and I've become accustomed to the extra functionality provided by its highlighting. Due to this problem, I have never been able to use Code Runner. |
I have the same problem. |
Any news on this issue? |
Depends on microsoft/vscode#19561 |
Microsoft seems to have closed microsoft/vscode#19561 with an API to specify output channels. Any update on the Code Runner end? Because I just confirmed (discovered the hard way) the issue still exists, Code Runner disables Output Colorizer. |
@formulahendry Any news on this issue? Many people use Code Runner and it's very bad that people have to disable it indefinitely until they need to use it, otherwise the Output Colorizer plugin would not work on a day to day basis. As @AEVJordan noted:
|
I published a PR here #1092, it solves both coloring and link detection errors and makes it compatible with colorizer extensions. @formulahendry |
I've been having trouble lately with not seeing any colors in the output window of VSCode.
Version 1.9.0-insider
Commit 3af0e9d6b79145011a7be3970c1d4b83d69b0443
Date 2017-01-27T10:46:43.625Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0
Code Runner - version 0.6.7
I usually use IBM's Output Colorizer extension to get colors in the output, but recently I stopped seeing colors.
I started disabling extensions until the colors showed up again, and after disabling Code Runner I could see colors again.
Code Runner contributes the code-runner-output language to be able to colorize the output as well, so I think VSCode might only be able to have one language at a time for colorizing the output contents.
This is mostly just an fyi for the maintainers and others who might be having a similar issue.
The text was updated successfully, but these errors were encountered: