mirror of
https://https.git.savannah.gnu.org/git/bash.git
synced 2026-07-08 21:00:48 +02:00
commit bash-20161122 snapshot
This commit is contained in:
+2
-1
@@ -2794,7 +2794,8 @@ Any incorrectly formed brace expansion is left unchanged.
|
||||
A \fB{\fP or \fB,\fP may be quoted with a backslash to prevent its
|
||||
being considered part of a brace expression.
|
||||
To avoid conflicts with parameter expansion, the string \fB${\fP
|
||||
is not considered eligible for brace expansion.
|
||||
is not considered eligible for brace expansion, and inhibits brace
|
||||
expansion until the closing \fB}\fP.
|
||||
.PP
|
||||
This construct is typically used as shorthand when the common
|
||||
prefix of the strings to be generated is longer than in the
|
||||
|
||||
+2
-1
@@ -1766,7 +1766,8 @@ in the result. It is strictly textual. Bash
|
||||
does not apply any syntactic interpretation to the context of the
|
||||
expansion or the text between the braces.
|
||||
To avoid conflicts with parameter expansion, the string @samp{$@{}
|
||||
is not considered eligible for brace expansion.
|
||||
is not considered eligible for brace expansion,
|
||||
and inhibits brace expansion until the closing @samp{@}}..
|
||||
|
||||
A correctly-formed brace expansion must contain unquoted opening
|
||||
and closing braces, and at least one unquoted comma or a valid
|
||||
|
||||
Reference in New Issue
Block a user