[Octave-bug-tracker] [bug #56224] [Windows] Displaying char([194 160]) causes all following commands to result in just a prompt

[Markus Mützel]

Follow-up Comment #12, bug #56224 (project octave):

IIUC, the byte sequences that break the console on Windows 10 (and earlier)
are either invalid UTF-8 byte sequences or some other special characters
(e.g., char([194 160]) is the NO-BREAK SPACE).

I'm inclined to think that the console host didn't handle that kind of input
gracefully in those versions of Windows. In Windows 11, those invalid byte
sequences result in the REPLACEMENT CHARACTER � being displayed.

There's probably not much we can do about this (short of implementing some
kind of "string sanitizer" before sending those sequences to the console). But
I guess this error would disappear with the new cross-platform command
widget.

Btw: Do the arrow keys still work in the GUI and the CLI with that version of
Octave?



    _______________________________________________________

Reply to this item at:

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

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