On Thu, Oct 05, 2006 at 12:23:41AM +0200, Reuti wrote:
[...]
> Curly braces expansion only works with at least one comma
> (,). This also works, if the appears at least once
> inside some apostrophes and has no function.
>
> Repeat-By:
> [EMAIL PROTECTED]:~> bash --versio
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On Fri, Oct 06, 2006 at 11:55:27AM +0200, [EMAIL PROTECTED] wrote:
[...]
> Repeat-By:
>
> $ echo $(
> > case a in
> > 1) :;;
> bash: syntax error near unexpected token `;;'
>
> The closing `)' is misinterpreted as being the end of the `$('
> s
[EMAIL PROTECTED] writes:
> $ echo $(
> > case a in
> > 1) :;;
> bash: syntax error near unexpected token `;;'
Use (1) instead.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP
Stephane Chazelas wrote:
On Thu, Oct 05, 2006 at 12:23:41AM +0200, Reuti wrote:
[...]
Curly braces expansion only works with at least one comma
(,). This also works, if the appears at least once
inside some apostrophes and has no function.
Repeat-By:
[EMAIL PROTECTED]:
mwoehlke <[EMAIL PROTECTED]> writes:
> ...but doesn't that mean that '{"x,x"}' should expand as '{x,x}'
It does.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5
Andreas Schwab wrote:
mwoehlke <[EMAIL PROTECTED]> writes:
...but doesn't that mean that '{"x,x"}' should expand as '{x,x}'
It does.
Huh?
$ echo {"x,x"} # expected result: '{x,x}'
x,x
$ echo $BASH_VERSION
3.1.17(3)-release
That doesn't look like '{x,x}' to me... it looks like 'x,x', which
mwoehlke <[EMAIL PROTECTED]> writes:
> Andreas Schwab wrote:
>> mwoehlke <[EMAIL PROTECTED]> writes:
>>
>>> ...but doesn't that mean that '{"x,x"}' should expand as '{x,x}'
>>
>> It does.
>
> Huh?
In the forthcoming 3.2 release anyway, so this bug has apparently already
been fixed.
Andreas.
--
Andreas Schwab wrote:
mwoehlke <[EMAIL PROTECTED]> writes:
Andreas Schwab wrote:
mwoehlke <[EMAIL PROTECTED]> writes:
...but doesn't that mean that '{"x,x"}' should expand as '{x,x}'
It does.
Huh?
In the forthcoming 3.2 release anyway, so this bug has apparently already
been fixed.
Ah, o