I see this issue mentioned here: https://lists.gnu.org/archive/html/bug-bash/2018-03/msg00168.html
But not clear if this got fixed at some point? > On Jun 29, 2022, at 1:57 PM, Sergei Gerasenko <[email protected]> wrote: > > Hello, > > It seems that with version 7 of readline this binding doesn't work as > expected: > > set keymap vi-insert > "\e[200~": bracketed-paste-begin > > What happens I think is that the \e is interpreted as a literal escape and > the user is kicked into the vi-command mode. Here’s my understanding of what > happens then: > > 1. The 200 (or "[200~”?) is then fed into readline in the vi-command mode. > 2. That is interpreted as a numbered-argument command and the user sees > “(arg: 200)” at the beginning of the line. > > One workaround I’ve seen is to do this: > > set keymap vi-command > "[200~": bracketed-paste-begin > > That does help in that the text is pasted without the “(arg: 200)” marker > appearing. But then if one presses ANY key, a bell is heard and the input is > ignored. Only when a key is pressed another time, that it’s interpreted. > > The system I’m seeing this on is CentOS 8. > > Is this a known issue or is it me? > > Thanks! > S
