[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible bug when combining Bash's process substitution with HERE-do
From: |
Dan Douglas |
Subject: |
Re: Possible bug when combining Bash's process substitution with HERE-document? |
Date: |
Wed, 18 Jun 2014 15:27:43 -0500 |
On Wed, Jun 18, 2014 at 2:49 PM, Chet Ramey <chet.ramey@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
- Possible bug when combining Bash's process substitution with HERE-document?, Tim Friske, 2014/06/17
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Dan Douglas, 2014/06/18
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Chet Ramey, 2014/06/18
- Re: Possible bug when combining Bash's process substitution with HERE-document?,
Dan Douglas <=
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Chet Ramey, 2014/06/18
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Tim Friske, 2014/06/19
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Dennis Williamson, 2014/06/19
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Greg Wooledge, 2014/06/20
- Re: Possible bug when combining Bash's process substitution with HERE-document?, Chet Ramey, 2014/06/20