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

[Marshall]

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

I traced the known causes of disabling of color in the console back to
system(...) calls. 

1) xlsread() disables color when system('unzip ...') called in unpack(). 

2) The random fact that some errors disable color and some don't can be traced
as far as I can tell to errors due to improper function call usage, which
trigger print_usage() calls which I trace down to color being disabled after
system('makinfo ...') in __makeinfo__(). 

This means system(...) calls both enable or disable ANSI escape character
interpretation depending on what is run by the system() command. 

Another odd behavior I noticed is that the ANSI coloring can persist after
ANSI escape codes are no longer interpreted.
 

system("");
fprintf(2,'\033[01;31mredtext\n'); 
isnan(); %comment this out to have the next command work
fprintf(2,'\033[01;30mstill red text but should be black\n');


In the above the red coloring triggered by the escape sequence persists even
though the second set isn't recognized.

    _______________________________________________________

Reply to this item at:

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

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