[Octave-bug-tracker] [bug #51272] Color in Command line color not enabled initially

[Marshall]

Follow-up Comment #3, bug #51272 (project octave):

I'm glad to see work is happening (or happened) on this. From looking at the
comments on the patch, it supports what I've learned that Windows didn't used
to support ANSI escape sequences at all. Windows 10 just recently began to
support ANSI escape sequences, so now color can show up. I tested on my Win7
machine and it wouldn't show color even with the use of any of the tricks that
I mentioned below.

I had looked into what enables color in Windows this last week and found that
supposedly color is enabled by a specific SetConsoleMode call that switches it
on or off. I believe the system("") calls turn color on because processes run
by octave, such as the system call (or the output pager) turns that switch on,
and something in octave, perhaps errors, switches it off. It seems that it
should be easy to make sure the switch is set to on at octave startup and
isn't turned off by error calls.

I would really like to see red errors, and other colored output in the windows
terminal, which doesn't happen at all right now. Now you know windows 10 can
support it, maybe you can enable color for Win 10 (or have an option so a user
can enable it)? 

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51272>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/