On Wed, Jun 18, 2014 at 2:49 PM, Chet Ramey <chet.ra...@case.edu> wrote: > Yes, since bash can parse the same construct without any problems if you > use command substitution, it looks like a bug. I'll take a look.
It brings to mind all those unbalanced paren case..esac bugs that affected every shell ever. I suppose this might qualify as a bug too? bash -c 'cat <(case x in x) echo test; esac)'; sleep 1 bash: process substitution: line 0: syntax error near unexpected token `newline' bash: process substitution: line 0: `case x in x' cat: /dev/fd/63 echo test; esac): No such file or directory
