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

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

[Octave-bug-tracker] [bug #54391] Incorrect result when attempting to ty


From: Alan W. Irwin
Subject: [Octave-bug-tracker] [bug #54391] Incorrect result when attempting to type or paste UTF-8 Cyrillic text into octave CLI
Date: Fri, 27 Jul 2018 04:28:11 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.10.1 Chrome/61.0.3163.140 Safari/537.36 Konqueror (WebEnginePart)

Follow-up Comment #2, bug #54391 (project octave):

Mike Miller asked:
> Have you tried experimenting with different readline settings?

Not until now when I tried your suggestion of -no-line-editing which I confirm
on my (Debian Buster) system allows cut and paste
of

x="Частота"

to work properly with the octave CLI.

I also tried the experiment of cutting and pasting the above command in the
Python CLI (since I am virtually positive that the Python CLI
uses the readline library).  In that case I got the (correct)
result:

>>> x="Частота"
>>> x
'\xd0\xa7\xd0\xb0\xd1\x81\xd1\x82\xd0\xbe\xd1\x82\xd0\xb0'

So I am fairly sure the issue is not due to some bug in libreadline, but might
be caused by some difference between how the Python and Octave CLI's use
libreadline.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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