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

[Marshall]

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

                 Summary: Color in Command line color not enabled initially
                 Project: GNU Octave
            Submitted by: marsian
            Submitted on: Mon 19 Jun 2017 11:10:44 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Marsian
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

I'm using Windows 10, and haven't tested this on Win7 yet. I found a bug
that's been bothering me for a while where I happily discovered I could show
things in color on the commnad prompt in the gui using the techniques of
https://www.gnu.org/software/octave/doc/interpreter/Customizing-the-Prompt.html,


PS1 ('\[\033[01;31m\]\s:\#> \[\033[0m\]')

But later no coloring would work. I thought some windows update must have been
the culprit or maybe it was because I recently changed from a windows 7 to
windows 10 machine, but couldn't get color to work when I went back and tested
it on a different windows 7 machine. Finally, today color accidentally
appeared on the command line due to output of a system() call, so I knew color
WAS working after all, tried the above command, and it worked again. After
restarting octave, color was gone again. I narrowed it down so I can reliably
get color to be enabled by calling certain functions in octave, but color is
never enabled at startup. The following things enable color: calling any
system() command, a print() command (don't know if all print calls do it,
because I traced it down to a non-documented form of a call to drawnow() ),
and any output that uses the pager (e.g. dir(), path(), and long output to the
command window: calling more off before color is enabled will disable any of
the long output from enabling color.

Color should be enabled at octave startup, rather than randomly after some
other function enables color at the command window inside of it.




    _______________________________________________________

Reply to this item at:

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

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