Re: command_not_found_handle strange behaviour

[Chet Ramey]

On 3/29/18 12:08 PM, Eduardo A. Bustamante López wrote:
> On Wed, Mar 28, 2018 at 06:42:21PM +0300, Кириллов Дима wrote:
> [...]
>> Bash Version: 4.4
>> Patch Level: 19
>> Release Status: release
>>
>> Description:
>>      I can't understand why read works without subshell before it, 
>> but with subshell before read it stops
>>
>>     command_not_found_handle()
>>     {
>>         (true) # subshell call
>>         read line
>>         echo "$line"
>>     }
>>
>>   bash-4.4$ foo
>>   
>>   [1]+  Stopped                 foo
>>
>> And without subshell call it works fine:
> 
> I can reproduce this.
> 
> 
> A few observations:

These are mostly spot-on, except that it depends on whether the shell has
job control enabled, not whether it's interactive (that's when it tries to
manipulate process groups), though the behavior is slightly different.

It will be fixed in the next devel branch push.

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