I am trying to get 256 colors under Cygwin while running cmder. Generally, what I am doing is opening a terminal session in Windows 10 by typing "cmd" into Start. If I need to open a Cygwin terminal, I generally enter "bash" into that cmder instance.
When I run tput colors
from within either the cmder prompt or the Cygwin terminal running within cmder, the system returns 8
.
I have reviewed the following similar threads and references: ConEmu + ls -- 256 colors not working https://conemu.github.io/en/CygwinMsysConnector.html
(some links omitted due to low reputation limitations, see comments, but I am familiar with how Cygwin processes ANSI internally before passing it, parsed, to a ConEmu terminal)
I have downloaded the cygwin/msys connector and, indeed, tput colors
returns 256 when I run the connector. What I would like to do is find a way to integrate this connector more directly into my workflow. I have environment variables that tie Cygwin more directly into my Windows terminal environment within cmder and sometimes run Cygwin commands from outside of a bash prompt, e.g. running vim on some file from a windows prompt, so simply running the connector every time I'd like access to the Cygwin bash isn't quite a complete solution for me. I'd like to know how to "wire up" this connector more directly so that it's running automatically, in the background, in lieu of running bash directly. I don't know if that makes any sense at all.
What I'm looking for is what environment variables, tasks, etc I need to set specifically to make this linkage happen more seamlessly.
edit: I realized it may be important to point out that I have cygwin's path put into my system environment variables.
TERM=xterm-16color
I have on mintty$ tput colors
16