That's because your syntax is incorrect.
First, there's no "$e]0"; it should be "$e[0".
Second, you're setting a color and then turning it off and setting a
different color before displaying anything. If you want to combine them (to
make a bright color), you do it in a single escape sequence; i.e.
See " ANSI X3.64 Command Reference" in the help for details.
On Mon, 11 Jul 2011 23:08:48 -0400, roytam1 <> wrote:
|---Quote (Originally by rconn)---
|It would be pointless, because TCC has ANSI support built-in (and has for a number of years).
|But the color is different from ANSICON/PuTTY:
Make a color bright with, for example, "$e[33;1m". The "$e[33m$[1m" which you
use is odd in my experience. I don't believe the standard is specific about
what happens if you use "$e[1m" alone.
According to Wiki,
CSI n [;k] m SGR – Select Graphic Rendition Sets SGR parameters, including
text color. After CSI can be zero or more parameters separated with ;. With no
parameters, CSI m is treated as CSI 0 m (reset / normal), which is typical of
most of the ANSI escape sequences.
$e]0 (Operating System Controls) is for changing the title, ansicon is in act but it can't take over TCC's ANSI logics.
I couldn't even get it to run. Here, COMSPEC is not set (except by individual shells). ANSICON.C has (essentially)If you want to use ansicon (instead of using the correct TCC syntax), you'll have to get the ansicon author to fix his bugs.
WCHAR *cmd; // ... // if COMSPEC is not set cmd = L"cmd"; // ... CreateProcess(NULL, cmd, ...
Well I just discovered that using ansicon to supplement built-in ANSI support isn't pointless after all. Unlike built-in ANSI, which isn't available to external programs according to help topic "ANSI X3.64 Command Reference", ansicom enables ANSI support for external programs that run in the console.It would be pointless, because TCC has ANSI support built-in (and has for a number of years).
Which brings me to my question. Is there a built-in way to paginate files that include embedded ANSI codes? I tried //option ANSI=Yes + LIST or VIEW, but LIST and VIEW display raw control characters. TYPE alone displays ANSI escapes correctly but when I pipe it into LIST /S I get raw control characters again, likewise piping TYPE into MORE. So far the only working solution I could find is ansicon + MORE.