Hi, RHEL 7 doesn’t have this problem. I suspect it’s only readline 7.0.
bind -P reports: vi-arg-digit can be found on "1", "2", "3", "4", "5", … On the non-affected systems it’s not bound to anything. That must be the culprit? What’s the most effective way to “unbind” that? “bind -r vi-arg-digit” doesn’t seem to help Thanks Chet! > On May 6, 2022, at 2:50 PM, Chet Ramey <chet.ra...@case.edu> wrote: > > On 5/6/22 3:16 PM, Sergei Gerasenko wrote: >> Hello, >> I’m seeing strange behavior in bash on CentOS 8. The version of bash there >> is 4.4.20(1). The 4.2.46(2) version on CentOS 7 doesn’t have this problem. >> The versions of readline are 6.2 and 7.0 respectively. The problem is that >> when vi-mode is on and bracketed paste is enabled in .bashrc with: >> bind 'set enable-bracketed-paste on’ >> … pasting while in the INSERT mode will result in: a bell + “(arg: 200)” >> I suspect this is because the bracketed paste escape sequence has 200 in it. >> Namely, "ESC [ 200 ~”. Is this a known bug and is there a workaround? The >> readline version on C8 is readline-7.0. > > I can't reproduce this using bash-4.4.23 on macOS or RHEL 7. > > It looks like the key sequence that begins a bracketed paste isn't bound to > the readline command that reads the pasted text. That happens by default in > bash-4.4 as distributed; maybe CentOS disables it for some reason. > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
