VT100 commands in console windows

  • Thread starter Thread starter Default User
  • Start date Start date
D

Default User

I'd like to be able to use VT100 escape sequences in the output window
when executing a program from an IDE (I'm using VC++ 6) or from
double-clicking the resulting .exe. I found some info for setting up
DOS windows to do that, the old ANSI.SYS thing, but it didn't seem to
affect these console windows, nor can the program run in the DOS window.

Any tricks for doing this? All I really want to do is make the text
(which is some developer's output) more readable. Data is updated at
about 20Hz, so the text display in the console is kind of fluttery and
hard to read at times. I don't wish to use any of the programing
solutions for accessing Windows, for portability reasons, so if I can't
use a few simple VT100 sequences I'll just bag it and suffer.

Note, this message is cross-posted as follows, as I was unsure of the
best newsgroup.

microsoft.public.windowsxp.configuration_manage
microsoft.public.windowsxp.general
microsoft.public.windowsxp.customize

I will monitor all, so feel free to reduce the group list if any are
inappropriate.

Thanks.


Brian
 
Hi,

Default said:
I'd like to be able to use VT100 escape sequences
in the output window when executing a program from an
IDE (I'm using VC++ 6) or from double-clicking the
resulting .exe.
Click to expand...

Unfortunately, Win32 console does not have anything like ANSI.SYS that I am
aware of.
I don't wish to use any of the programing
solutions for accessing Windows, for portability
reasons...
Click to expand...

You could do it and preserve portability through conditional compiling (some
#defines and #ifdefs), but whether it's worth the trouble (not a lot of
trouble, but still some) is certainly your call.
 
Chris said:
Hi,



Unfortunately, Win32 console does not have anything like ANSI.SYS
that I am aware of.
Click to expand...

I was afraid of that. It didn't look good when massive googling failed
to turn up anything.
You could do it and preserve portability through conditional
compiling (some #defines and #ifdefs), but whether it's worth the
trouble (not a lot of trouble, but still some) is certainly your call.
Click to expand...


I'll just live with it the way it is. It's only the development display.



Brian
 
Back
Top