GNU bash, version 4.2.24(1)-release (i686-pc-linux-gnu)
Take the following example, assumed to be run in an empty directory:
$ mkdir a
$ echo **
a
$ echo **/**
a a
$ echo **/**/**
a a a
I would expect the result to be just 'a' in all cases.
You also get back a null filename, as shown by
$ fo
On 12/1/12 1:00 AM, Dan Douglas wrote:
>
> I believe one of the motivations for named FDs other than automatic FD
> allocation, and the reason they remain open, was probably to deal with
> organizing and grouping coprocesses so that you could follow the variable
> names rather than the FDs dir
