Re: New feature in bash 5.1/readline-8.1 rc1 breaks python-pexpect

[Chet Ramey]

On 10/28/20 10:51 AM, Dr. Werner Fink wrote:
> On 2020/10/28 10:23:57 -0400, Chet Ramey wrote:
>> On 10/16/20 9:28 AM, Chet Ramey wrote:
>>> On 10/16/20 9:16 AM, Dr. Werner Fink wrote:
>>>
>>>> Also a warning hint in the manual page could
>>>> help users before enabling this feature :)
>>>
>>> I agree, and the manual page in the release will reflect bracketed paste's
>>> default setting. However, readline doesn't try to enable bracketed paste if
>>> tcgetattr fails, which it will on an fd that's not a terminal, so I am
>>> fairly sure that expect/pexpect use ptys to masquerade as terminals.
>>>
>>> The biggest problem with bracketed paste is that right now, there's simply
>>> no way to determine whether or not a particular terminal supports it.
>>
>> I wonder if it would make sense for bash to compile its version of readline
>> with bracketed paste on by default, but the standalone readline library
>> version have it off. Or is that too clever by half?
> 
> Ohmm ... this makes no diffference here as bash (and all other tools)
> uses, if ever possible, the system libraries by policy.  And the readline
> library is a system library.  That means if there is a security issue within
> such a system library it has to be fixed only once.

Then it seems like the best way to address these competing requirements is
to allow readline to be configured with the default one way or another. I
already added a #define that can be used to set the default value of
enable-bracketed-paste.

-- 
``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/