Re: Possible bug for nested curly brace expansion

On 2025-03-06 11:58, Lawrence Velázquez wrote: > On Thu, Mar 6, 2025, at 1:48 PM, microsuxx wrote: >> {0} is no expansion >> {0,} is >> it must be 2+ > > And this is documented. It is not a bug. > > A correctly-formed brace expansion must contain unquoted > opening and closing braces

Re: Possible bug for nested curly brace expansion

On Thu, Mar 6, 2025, at 9:06 PM, Kaz Kylheku wrote: > But Bash cannot do this. The reason is that brace expansion is already > a deviation from POSIX. POSIX.1-2024 does permit brace expansion syntax as an extension, although it doesn't use the term "brace expansion" or prescribe any specific seman

Possible bug for nested curly brace expansion

$ bash --version GNU bash, version 5.2.37(0)-release (amd64-portbld-freebsd14.1) Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY,

Re: Possible bug for nested curly brace expansion

On Thu, Mar 6, 2025, at 1:48 PM, microsuxx wrote: > {0} is no expansion > {0,} is > it must be 2+ And this is documented. It is not a bug. A correctly-formed brace expansion must contain unquoted opening and closing braces, and at least one unquoted comma or a valid seque