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: Markus Mützel
Subject: [Octave-bug-tracker] [bug #54391] Incorrect result when attempting to type or paste UTF-8 Cyrillic text into octave CLI
Date: Sat, 22 Sep 2018 19:31:19 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Update of bug #54391 (project octave):

        Operating System:               GNU/Linux => Any                    

    _______________________________________________________

Follow-up Comment #7:

I don't know why we ever needed the hard-coded readline bindings in the first
place. Alt+P and Alt+N are already bound to
"non-incremental-reverse-search-history" and
"non-incremental-forward-search-history" by default. The only difference to
"history-search-backward" and "history-search-forward" seems to be that the
latter should only match the start of a line. [1] (But that isn't how Alt+P
behaved for me before the patch.)

Readline 6.3 and newer should be handling UTF-8 charsets correctly
automatically. At least as long as we (or the user) aren't messing with the
meta-settings.
There still seems to be a problem with rl_add_defun and Meta-key shortcuts.
It might be best to remove the calls to rl_add_defun with Meta-key shortcuts
entirely. If it should be necessary, a user could still switch back to the old
functions in their ~/.inputrc with:

"\M-p": history-search-backward
"\M-n": history-search-forward


With the patch applied I can paste the Cyrillic string from comment #0 also in
Octave for Windows (cross-compiled with readline 6.3 from bug #47571) which
previously failed as well.
Alt+P and Alt+N never worked for me on Windows. (But I don't know to which key
the Meta key corresponds on Windows.)

[1]: https://tiswww.case.edu/php/chet/readline/readline.html#SEC15

    _______________________________________________________

Reply to this item at:

  <https://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]