On 3/16/18 3:55 PM, Greg Wooledge wrote:
>> That
>> sounds like quite a 'gotcha' and isn't mentioned in the man page
>> documentation for mapfile. Do you think it should be? Should I continue
>> this now on-list and ask for it to be mentioned?
Each process in a pipeline is run in a subshell (`las
Boruch Baum wrote:
I'm afraid what prompted me to file the report was something more
subtle. Upon trying my test one-liner on a second virtual terminal, the
one-liner worked, so I'm now trying to figure out what settings might
affect the behavior. My test one-liner is:
printf "aa bb\n cc
On Fri, Mar 16, 2018 at 03:45:42PM -0400, Boruch Baum wrote:
> On 2018-03-16 14:59, Greg Wooledge wrote:
> > wooledg:~$ set +m
> > wooledg:~$ echo hello world | readarray; declare -p MAPFILE
> > declare -a MAPFILE=([0]=$'hello world\n')
> >
> > lastpipe will typically work in a script, because job
On Fri, Mar 16, 2018 at 02:59:53PM -0400, Greg Wooledge wrote:
> On Fri, Mar 16, 2018 at 02:06:09PM -0400, Boruch Baum wrote:
> >echo $IFS |xxd
> >: 0a
>
> This command will never reveal any information, period.
I was slightly mistaken there. It actually reveals the number of
non
You forgot to Cc: the mailing list. I think this was on bug-bash...?
On Fri, Mar 16, 2018 at 02:06:09PM -0400, Boruch Baum wrote:
> On 2018-03-16 09:22, Greg Wooledge wrote:
> > On Fri, Mar 16, 2018 at 09:14:13AM -0400, Boruch Baum wrote:
> > > In GNU bash, version 4.4.18(1)-release (x86_64-pc-li
On Fri, Mar 16, 2018 at 09:14:13AM -0400, Boruch Baum wrote:
> In GNU bash, version 4.4.18(1)-release (x86_64-pc-linux-gnu), the first
> line of the documentation for readarray / mapfile states:
>
>Read lines from the standard input ...
>
> However, it doesn't seem to accept input from a pipe
