[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #56224] [Windows] Displaying char([194 160]) c
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #56224] [Windows] Displaying char([194 160]) causes all following commands to result in just a prompt |
Date: |
Tue, 29 Nov 2022 06:28:36 -0500 (EST) |
Update of bug #56224 (project octave):
Status: Confirmed => Ready For Test
_______________________________________________________
Follow-up Comment #7:
Could anyone affected by this bug please check if it still occurs with a
recent nightly build of Octave from the *mxe-default* category:
https://buildbot.octave.space/#/download
In particular, it would be interesting to hear if the arrow keys are still
working to access the history (in the GUI and in the CLI). Additionally, does
entering non-ASCII characters in the command window widget of the GUI work
correctly? Does it still crash the Windows console (i.e., freeze the command
window)?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56224>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #56224] [Windows] Displaying char([194 160]) causes all following commands to result in just a prompt,
Markus Mützel <=