[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Filename expansion bug

From: Stephane Chazelas
Subject: Re: Filename expansion bug
Date: Thu, 8 Aug 2019 16:07:39 +0100
User-agent: NeoMutt/20171215

2019-08-08 10:38:48 -0400, Greg Wooledge:
> > shopt -s failglob
> > command="echo xyz\(\)"
> > $command
> > ```
> > 
> > And it was working fine. But somewhere between bash version 4 and 5 I
> > realized it generates an error:
> > no match: xyz\(\)
> And my personal response for this variant of the issue: stop putting
> shell commands in string variables and then trying to run them with
> unquoted parameter expansion.  See:

While I'd agree in this case, note that the austin-group thread
was mentionning a very similar case:

That was in autoconf's configure script (including the one
shipped with bash) that is /broken/ by that change in 5.0:

as_echo='printf %s\n'
$as_echo x

now runs:

printf '%sn' x

if there's a file called %sn in the current directory and

printf '%s\n' x


(and would cause an error with failglob and run printf x with

In that case, it's not because the autoconf authors don't know
any better but because at that point in the script where
$ac_echo is defined, they're trying to support ancient shells
that don't have function support.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]