[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47571] Problem entering non-ASCII-character (
[Octave-bug-tracker] [bug #47571] Problem entering non-ASCII-character (umlaut) in command line
Sun, 9 Jun 2019 09:59:51 -0400 (EDT)
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Update of bug #47571 (project octave):
Summary: [MXE-Octave] Problem entering non-ASCII-character
(umlaut) in command line => Problem entering non-ASCII-character (umlaut) in
Follow-up Comment #42:
Now that we are using a newer version of readline, I thought it might be
easier to enable entering 8bit characters in the command window.
The attached patch sets the necessary flags in our inputrc. With this change,
entering 8bit characters like "ä", "Ö", "ß" or "§" with a German keyboard
layout is possible.
Remaining issues include:
- Any 8bit character appears on screen only after an additional key stroke for
a 7bit character.
- Entering two 8bit characters in a row breaks the command window: it is no
longer possible to enter anything.
- Using the left arrow keys to reverse over an 8bit character messes up the
cursor position. With the cursor left of an 8bit character, entered characters
override characters on-screen. These characters appear at an unexpected
position in the resulting string (after hitting enter).
- Pasting strings with 8bit characters into the command window doesn't work at
all. After trying to paste a string including an 8bit character, the paste
functionality seems to be broken for the remainder of the Octave session.
I am not sure whether these are issues with readline or with our
implementation of the command window.
Additional Item Attachment:
File name: bug47571_rl_8bit.patch Size:1 KB
Reply to this item at:
Message sent via Savannah
|[Prev in Thread]
||[Next in Thread]|
- [Octave-bug-tracker] [bug #47571] Problem entering non-ASCII-character (umlaut) in command line,
Markus Mützel <=