[issue42626] readline history, vi-editingmode and ANSI color codes bug

Joakim Nilsson added the comment: Yes, I have noticed that too, and I agree, not as bad as if it was garbled, but still an annoyance. On Fri, Jul 30, 2021 at 1:34 AM Andrei Kulakov wrote: > > Andrei Kulakov added the comment: > > Joakim: by the way, what I was able to reproduce is just a

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Andrei Kulakov added the comment: Joakim: by the way, what I was able to reproduce is just a visual bug. IOW, the text is still the same and all there in the buffer, but it shows up only after a combination of rightward movement and 'a', and a copy of it shows up on the left side. So it's

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Andrei Kulakov added the comment: Also this bug happens on both iterm2 and terminal on MacOS, but note that on 'terminal', it's impossible to ctrl-c or ctrl-z out of the test script, so if you test it, you will need to close the window or the tab, and lose shell history and background jobs,

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Andrei Kulakov added the comment: I was able to reproduce something very similar, and I believe essentially the same issue perhaps varying due to config. I think I've actually seen similar glitches with python command line readline handling of k. So, entering 1234 always works fine. The

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Joakim Nilsson added the comment: Sorry, my mistake. If you remove the last line "input()" from readline.py, it should be reproducible. Tested on Python 3.9.2. Link to video demonstration of the bug: http://nijoakim.com/readline-example.mp4. -- Added file:

[issue42626] readline history, vi-editingmode and ANSI color codes bug

Andrei Kulakov added the comment: I can't reproduce on MacOS in both Py 3.9.1 and in dev version. Works fine, I can erase everything after '2' and before it. -- nosy: +andrei.avk ___ Python tracker

[issue42626] readline history, vi-editingmode and ANSI color codes bug

New submission from Joakim Nilsson : Tested on Debian Bullseye with Python 3.9. If 'set editing-mode vi' is used in .inputrc and the attached program is run, a bug occurs when navigating the readline history. It seems only to occur when ANSI color escape characters are input to the 'input()'