SlickEdit Community
SlickEdit Product Discussion => SlickEdit® => Topic started by: texasaggie97 on October 12, 2017, 09:16:25 PM
-
I am using Windows 10 x64 1703, including Windows Subsystem for Linux.
I am calling into WSL using a bash command and would like to get the color output I can get when using bash directly.
I can force color output from the command but the build window doesn't show it.
You can see what I am talking about in the two screenshots.
Should this work? If so I can keep trying to see what I am doing wrong. Otherwise, can it work in the future?
-
I'd really like to be able to see the colors in the build window as well.
I wrote a similar request in this post: https://community.slickedit.com/index.php?topic=14848.0
-
Agreed.
I am used to it but it feels so unprofessional when I have people looking over my shoulder at my compilations. They laugh and wonder why I still using an editor from the 1990s before compilers starting outputting in color... :-[
-
A corollary to this request is this: In addition to displaying my builds in the process buffer, I also save them in a log file. I would like to have a file type that can color based on the control codes, so that when I view these log files in an editor window I can see the colors properly. Perhaps the default coloring for the "process buffer file type" can be to color based on the control codes from the terminal, and then I could assign files with ".log" extension to have this process buffer file type to get colored properly.
-
Will v24 support having colors in the process buffer/Build output window?
This is another feature I've been wanting for a very long time. Its been requested on numerous threads:
https://community.slickedit.com/index.php?topic=16349.0
https://community.slickedit.com/index.php/topic,16159.msg62156.html#msg62156
https://community.slickedit.com/index.php/topic,14848.0.html
color codes:
http://tldp.org/HOWTO/Bash-Prompt-HOWTO/c327.html
https://misc.flogisoft.com/bash/tip_colors_and_formatting
-
This is still on our todo list. Sorry it's not implemented already.
-
Maybe the new Microsoft Terminal and the new Console APIs they have added (at least for Windows) will help? https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/