[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: incorrect brace expansion
From: |
Mike Frysinger |
Subject: |
Re: incorrect brace expansion |
Date: |
Sun, 29 Jan 2006 17:37:56 -0500 |
User-agent: |
KMail/1.9 |
On Sunday 29 January 2006 17:25, Bob Proulx wrote:
> The bash manual documents this as "Patterns to be brace expanded take
> the form of an optional PREAMBLE, followed by either a series of
> comma-separated strings or a sequnce expression between a pair of
> braces, followed by an optional POSTSCRIPT." Your example did not
> have either comma-separated strings nor a sequence and therefore does
> not qualify for brace expansion and should have been left verbatim.
> And yet bash did brace expansion anyway. That is an inconsistency.
a-{b}-c was not brace expanded, ok, good
a-{b{d,e}}-c was "expanded" too many times ... the output should have been
a-{bd}-c a-{be}-c ... just cause csh does it differently doesnt really matter
imo
as you pointed out, the docs say that the brace expansion should only happen
when commas or sequence expressions are used, and while the inner braces used
commads, the outer braces did not
-mike
- incorrect brace expansion, Tim Waugh, 2006/01/27
- Re: incorrect brace expansion, Bob Proulx, 2006/01/28
- Re: incorrect brace expansion, Mike Frysinger, 2006/01/29
- Re: incorrect brace expansion, Bob Proulx, 2006/01/29
- Re: incorrect brace expansion,
Mike Frysinger <=
- Re: incorrect brace expansion, William Park, 2006/01/29
- Re: incorrect brace expansion, Chris F.A. Johnson, 2006/01/29
- Re: incorrect brace expansion, William Park, 2006/01/29
- Re: incorrect brace expansion, Mike Frysinger, 2006/01/29
- Re: incorrect brace expansion, William Park, 2006/01/29
- Re: incorrect brace expansion, Mike Frysinger, 2006/01/29
- Re: incorrect brace expansion, William Park, 2006/01/29
- Re: incorrect brace expansion, Chet Ramey, 2006/01/29