RE: bash will not link against ncursesw and readline in /usr/local

2018-11-14 Thread John Frankish
> > If ncursesw is now the default, maybe it would make sense to check for that > > rather than a symlink? > > > I added a check for it, but I think its impact will be minimal. > Thanks :)

Re: bash will not link against ncursesw and readline in /usr/local

2018-11-14 Thread Chet Ramey
On 11/14/18 1:07 AM, John Frankish wrote: > If ncursesw is now the default, maybe it would make sense to check for that > rather than a symlink? I added a check for it, but I think its impact will be minimal. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars

Re: bash will not link against ncursesw and readline in /usr/local

2018-11-14 Thread Chet Ramey
On 11/14/18 1:07 AM, John Frankish wrote: >>> Using bash-4.4.18 >>> Intel core i7 laptop running 32-bit or 64-bit linux Using gcc-8.2.0 >>> >>> The configure script does not find libncursesw on a system where >>> only the wide version of ncurses exists - even when readine is linked >>> against nc

Re: Strange behaviour from jobs -p in a subshell

2018-11-14 Thread Greg Wooledge
> >>> Consider the following script. While the 3 sleeps are running, both jobs > >>> -p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished, [...] ... hey, I think I just figured out the GOAL! You want to run a whole bunch of jobs in parallel, but only 3 at a time. Right? There a

Re: Strange behaviour from jobs -p in a subshell

2018-11-14 Thread Chet Ramey
On 11/14/18 4:48 AM, Christopher Jefferson wrote: > > On 13/11/2018 14:59, Chet Ramey wrote: >> On 11/13/18 4:28 AM, Christopher Jefferson wrote: >>> Consider the following script. While the 3 sleeps are running, both jobs >>> -p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished,

Re: Strange behaviour from jobs -p in a subshell

2018-11-14 Thread Christopher Jefferson
On 13/11/2018 14:59, Chet Ramey wrote: > On 11/13/18 4:28 AM, Christopher Jefferson wrote: >> Consider the following script. While the 3 sleeps are running, both jobs >> -p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished, >> jobs -p will continue to print the 3 PIDs of the done