Re: bracketed paste on 4.4.20(1)-release

[gerases]

Sounds great! Ic think i have enough to continue from here. Thanks again!

> On May 6, 2022, at 15:52, Chet Ramey <chet.ramey@case.edu> wrote:
> 
> On 5/6/22 4:08 PM, Sergei Gerasenko wrote:
>> Hi, RHEL 7 doesn’t have this problem. I suspect it’s only readline 7.0.
> 
> I mean I tried it on bash-4.4.23 built from sources on RHEL7, not whatever
> ancient version Red Hat ships. That bash-4.4 distribution uses a version of
> readline identical to what's distributed as readline-7.0.
> 
> 
>> 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?
> 
> Maybe, but I can't help you there. It's not like that in versions of
> bash-4.4 that I build from the sources I distributed.
> 
> 
>> What’s the most effective way to “unbind” that? “bind -r vi-arg-digit” 
>> doesn’t seem to help
> 
> Several problems. First, you should specify a keymap to unbind it in:
> 
> bind -m vi-insert
> 
> since the default keymap for bind may not be what you want. Second, -r
> takes key sequences; use -u to unbind by function name.
> 
> So
> 
> bind -m vi-insert -u vi-arg-digit
> 
> will probably do what you want, even though I suspect it's a red herring.
> What you should search for is whether bracketed-paste-begin is bound to
> a key sequence in the vi-insert keymap. I get
> 
> $ bind -m vi-insert -P | grep bracketed
> bracketed-paste-begin can be found on "\e[200~".
> 
> Chet
> -- 
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>         ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/