fix for invalid brace sequence expressions; cosmetic fix to help builtin; documentation and copyright updates; bump version to bash-5.3-rc1; cosmetic locale fixes

This commit is contained in:
Chet Ramey
2025-03-24 17:07:43 -04:00
parent c3997d51f8
commit e009d30dff
47 changed files with 1629 additions and 1884 deletions
+4 -4
View File
@@ -903,7 +903,7 @@ operators do not evaluate \fIexpression2\fP if the value of
the entire conditional expression.
.RE
.TP
\fBfor\fP \fIname\fP [ [ \fBin\fP [ \fIword .\|.\|.\&\fP ] ] ; ] \fBdo\fP \fIlist\fP ; \fBdone\fP
\fBfor\fP \fIname\fP [ [ \fBin\fP \fIword .\|.\|.\&\fP ] ; ] \fBdo\fP \fIlist\fP ; \fBdone\fP
First, expand The list of words following \fBin\fP, generating a list
of items.
Then, the variable \fIname\fP is set to each element of this list
@@ -917,7 +917,7 @@ The return status is the exit status of the last command that executes.
If the expansion of the items following \fBin\fP results in an empty
list, no commands are executed, and the return status is 0.
.TP
\fBfor\fP (( \fIexpr1\fP ; \fIexpr2\fP ; \fIexpr3\fP )) ; \fBdo\fP \fIlist\fP ; \fBdone\fP
\fBfor\fP (( \fIexpr1\fP ; \fIexpr2\fP ; \fIexpr3\fP )) [;] \fBdo\fP \fIlist\fP ; \fBdone\fP
First, evaluate the arithmetic expression \fIexpr1\fP according
to the rules described below under
.SM
@@ -3419,7 +3419,7 @@ For example, a\fB{\fPd,c,b\fB}\fPe expands into
.Q "ade ace abe" .
.PP
A sequence expression takes the form
\fB{\fP\fIx\fP\fB..\fP\fIy\fP\fB[..\fP\fIincr\fP\fB]}\fP,
\fIx\fP\fB..\fP\fIy\fP\fB[..\fP\fIincr\fP\fB]\fP,
where \fIx\fP and \fIy\fP are either integers or single letters,
and \fIincr\fP, an optional increment, is an integer.
When integers are supplied, the expression expands to each number between
@@ -4897,7 +4897,7 @@ The format of here-documents is:
.PP
The shell does not perform
parameter and variable expansion, command substitution,
arithmetic expansion, or pathname expansion is performed on
arithmetic expansion, or pathname expansion on
.IR word .
.PP
If any part of
+5 -4
View File
@@ -970,7 +970,7 @@ in @var{consequent-commands}, or zero if none was executed.
The syntax of the @code{for} command is:
@example
for @var{name} [ [in [@var{words} @dots{}] ] ; ] do @var{commands}; done
for @var{name} [ [in @var{words} @dots{}] ; ] do @var{commands}; done
@end example
Expand @var{words} (@pxref{Shell Expansions}), and then
@@ -985,10 +985,11 @@ The return status is the exit status of the last command that executes.
If there are no items in the expansion of @var{words}, no commands are
executed, and the return status is zero.
An alternate form of the @code{for} command is also supported:
There is an alternate form of the @code{for} command which is similar to the
C language:
@example
for (( @var{expr1} ; @var{expr2} ; @var{expr3} )) ; do @var{commands} ; done
for (( @var{expr1} ; @var{expr2} ; @var{expr3} )) [;] do @var{commands} ; done
@end example
First, evaluate the arithmetic expression @var{expr1} according
@@ -2069,7 +2070,7 @@ ade ace abe
@end example
A sequence expression takes the form
@code{@{@var{x}..@var{y}[..@var{incr}]@}},
@code{@var{x}..@var{y}[..@var{incr}]},
where @var{x} and @var{y} are either integers or letters,
and @var{incr}, an optional increment, is an integer.
When integers are supplied, the expression expands to each number between