octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #56757] Starting Octave, q>> undecodable token


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #56757] Starting Octave, q>> undecodable token: \001b(hex)[6\0020(hex) in command window
Date: Wed, 14 Aug 2019 11:12:55 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36

Follow-up Comment #1, bug #56757 (project octave):

Does this display every time you press Enter to get a new prompt in the
command window, or only once at startup?

The output you are seeing is not quite the same as bug #49385, compare


q>> undecodable token: \001b(hex)[6\0020(hex)


with


undecodable token: \001b(hex)[3m
undecodable token: \001b(hex)[23m


Your output is equivalent to "ESC [6 ". That seems like Octave or some program
started by Octave is printing an invalid control sequence.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56757>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]