VS Code developers lose useful color in build logs and ANSI files
Developers using VS Code report that build output in the output pane appears without color, while ANSI-colored files can display as gibberish in the editor. That makes build and test output harder to scan and pushes some developers to run commands manually in the integrated terminal instead. The reports also point to a gap between the terminal’s ANSI support and the editor’s output channels and buffers.
For VS Code developers working with builds, tests, and generated logs. Mentioned from Aug 2016 to Nov 2019 on GitHub.
6 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 4.7/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Currently all output goes to the output pane which shows just Black&White output which makes it hard to read
Right now, I just prefer to do ctrl + j , go to the terminal and just type make manually to have the colorized build
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks