search

IBM-Cloud / vscode-log-output-colorizer

Language extension for VSCode that adds syntax colorization for both the output/debug/extensions panel and *.log files.
https://marketplace.visualstudio.com/items?itemName=IBM.output-colorizer
MIT License
111 stars 28 forks source link

Output colorizer not working #21

Closed AnhQuanTran closed 6 years ago

AnhQuanTran commented 6 years ago

Hello I installed extension output colorizer and reload visual studio code after that. But it is not work. I use visual studio code version 1.15.1 x64 on windows 10 home Other extensions installed:

image

how to fix it Thank you for help

meydjer commented 6 years ago

Same here.

Visual Studio Code v1.20.1 on Linux Fedora 27 x64

Other extensions installed:

1503743_442328547_33403086

dmaglio commented 6 years ago

same issue for me... visual studio code v1.21.0 x86 on windows 7 x86 and base16 color theme capture color works until that point...

nonameolsson commented 6 years ago

Confirmed, doesn't work with VS Code 1.21.

AnhQuanTran commented 6 years ago

Cause python extension. Remove it or disable & restart.

dmaglio commented 6 years ago

@AnhQuanTran i don't have any python extension

xiaofengShi commented 6 years ago

the same error ,mac+vscode1.2.1, how to fix it

brentmitchell25 commented 6 years ago

I had to disable two extensions for it to work: Code Runner and Quokka.js

donniean commented 6 years ago

the same

triceam commented 6 years ago

Wow, all the way back from Feb and I'm just now seeing this issue... too many notifications. :)

Above comments are correct. There's most likely another VS Code extension that is overriding the colorization in the Output panel. There can only be one active colorizer in the output channel at any time - this is a limitation with VS Code itself. As mentioned above, the Python, Code Runner, and Quokka extensions will cause conflicts. There are also a few others that I can't remember the names of off hand. If you want the colorizer to have precedence, then you might have to disable other extensions.

dmaglio commented 5 years ago

new update: that "error" show in windows when i use git bash instead Windows cmd. maybe it's a git bash issue?

fredThem commented 2 years ago

I had to disable two extensions for it to work: Code Runner and Quokka.js

Disabling Code Runner alone fixed it for me

Leonid-98 commented 1 year ago

I had to disable two extensions for it to work: Code Runner and Quokka.js

Disabling Code Runner alone fixed it for me

Same for me

EricDuminil commented 1 year ago

I had to disable two extensions for it to work: Code Runner and Quokka.js

That's really too bad, because most of my output content comes from CodeRunner. :-/ If I have to choose between CodeRunner and OutputColorizer, I'll sadly stick to CodeRunner.

triceam commented 1 year ago

Unfortunately that's how it works in VS Code, and is beyond our control. You can only have one extension at a time that actively colorizes the output panel. The way they work is a bit of a hack in the first place, and it wasn't designed to allow for multiple colorization plugins.