commit bash-20190920 snapshot

doc/bash.1

@@ -5,12 +5,12 @@
 .\"	Case Western Reserve University
 .\"	chet.ramey@case.edu
 .\"
-.\"	Last Change: Mon Jul  8 15:14:50 EDT 2019
+.\"	Last Change: Fri Sep 20 15:30:19 EDT 2019
 .\"
 .\" bash_builtins, strip all but Built-Ins section
 .if \n(zZ=1 .ig zZ
 .if \n(zY=1 .ig zY
-.TH BASH 1 "2019 July 8" "GNU Bash 5.0"
+.TH BASH 1 "2019 September 20" "GNU Bash 5.0"
 .\"
 .\" There's some problem with having a `@'
 .\" in a tagged paragraph with the BSD man macros.
@@ -742,7 +742,9 @@ to be matched as a string.
 An additional binary operator, \fB=~\fP, is available, with the same
 precedence as \fB==\fP and \fB!=\fP.
 When it is used, the string to the right of the operator is considered
-a POSIX extended regular expression and matched accordingly (as in \fIregex\fP(3)).
+a POSIX extended regular expression and matched accordingly
+(using the POSIX \fIregcomp\fP and \fIregexec\fP interfaces
+usually described in \fIregex\fP(3)).
 The return value is 0 if the string matches
 the pattern, and 1 otherwise.
 If the regular expression is syntactically incorrect, the conditional
@@ -8494,7 +8496,7 @@ does not specify a valid job or
 .I jobspec
 specifies a job that was started without job control.
 .TP
-\fBgetopts\fP \fIoptstring\fP \fIname\fP [\fIargs\fP]
+\fBgetopts\fP \fIoptstring\fP \fIname\fP [\fIarg ...\fP]
 .B getopts
 is used by shell procedures to parse positional parameters.
 .I optstring
@@ -8540,8 +8542,9 @@ and \fIname\fP is set to ?.
 .sp 1
 .B getopts
 normally parses the positional parameters, but if more arguments are
-given in
-.IR args ,
+supplied as
+.I arg
+values,
 .B getopts
 parses those instead.
 .sp 1

doc/bashref.log

@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/MacPorts 2018.47642_7) (preloaded format=pdfetex 2019.1.16)  8 JUL 2019 15:16
+This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018/MacPorts 2018.47642_7) (preloaded format=pdfetex 2019.1.16)  20 SEP 2019 14:50
 entering extended mode
  restricted \write18 enabled.
  file:line:error style messages enabled.
@@ -286,7 +286,7 @@ Overfull \vbox (0.67252pt too high) has occurred while \output is active
 Here is how much of TeX's memory you used:
  4069 strings out of 497100
  47090 string characters out of 6206794
- 137042 words of memory out of 5000000
+ 137054 words of memory out of 5000000
  4846 multiletter control sequences out of 15000+600000
  34315 words of font info for 116 fonts, out of 8000000 for 9000
  51 hyphenation exceptions out of 8191
@@ -308,7 +308,7 @@ s/type1/public/amsfonts/cm/cmtt12.pfb></opt/local/share/texmf-texlive/fonts/typ
 e1/public/amsfonts/cm/cmtt9.pfb></opt/local/share/texmf-texlive/fonts/type1/pub
 lic/cm-super/sfrm1095.pfb></opt/local/share/texmf-texlive/fonts/type1/public/cm
 -super/sfrm1440.pfb>
-Output written on bashref.pdf (187 pages, 757503 bytes).
+Output written on bashref.pdf (187 pages, 757573 bytes).
 PDF statistics:
  2644 PDF objects out of 2984 (max. 8388607)
  2411 compressed objects within 25 object streams

doc/bashref.texi

@@ -1033,7 +1033,8 @@ An additional binary operator, @samp{=~}, is available, with the same
 precedence as @samp{==} and @samp{!=}.
 When it is used, the string to the right of the operator is considered
 a @sc{POSIX} extended regular expression and matched accordingly
-(as in @i{regex}3)).
+(using the @sc{POSIX} @code{regcomp} and @code{regexec} interfaces
+usually described in @i{regex}(3)).
 The return value is 0 if the string matches
 the pattern, and 1 otherwise.
 If the regular expression is syntactically incorrect, the conditional
@@ -1057,11 +1058,12 @@ string matching the @var{n}th parenthesized subexpression.
 
 For example, the following will match a line
 (stored in the shell variable @var{line})
-if there is a sequence of characters in the value consisting of
+if there is a sequence of characters anywhere in the value consisting of
 any number, including zero, of 
-space characters, zero or one instances of @samp{a}, then a @samp{b}:
+characters in the @code{space} character class,
+zero or one instances of @samp{a}, then a @samp{b}:
 @example
-[[ $line =~ [[:space:]]*?(a)b ]]
+[[ $line =~ [[:space:]]*(a)?b ]]
 @end example
 
 @noindent
@@ -1077,7 +1079,7 @@ expressions while paying attention to the shell's quote removal.
 Using a shell variable to store the pattern decreases these problems.
 For example, the following is equivalent to the above:
 @example
-pattern='[[:space:]]*?(a)b'
+pattern='[[:space:]]*(a)?b'
 [[ $line =~ $pattern ]]
 @end example
 
@@ -3574,7 +3576,7 @@ with a name that is not a shell function.
 @item getopts
 @btindex getopts
 @example
-getopts @var{optstring} @var{name} [@var{args}]
+getopts @var{optstring} @var{name} [@var{arg} @dots{}]
 @end example
 
 @code{getopts} is used by shell scripts to parse positional parameters.
@@ -3603,7 +3605,7 @@ and @var{name} is set to @samp{?}.
 
 @code{getopts}
 normally parses the positional parameters, but if more arguments are
-given in @var{args}, @code{getopts} parses those instead.
+supplied as @var{arg} values, @code{getopts} parses those instead.
 
 @code{getopts} can report errors in two ways.  If the first character of
 @var{optstring} is a colon, @var{silent}

doc/version.texi

@@ -2,10 +2,10 @@
 Copyright (C) 1988-2019 Free Software Foundation, Inc.
 @end ignore
 
-@set LASTCHANGE Mon Jul  8 15:10:15 EDT 2019
+@set LASTCHANGE Fri Sep 20 15:29:59 EDT 2019
 
 @set EDITION 5.0
 @set VERSION 5.0
 
-@set UPDATED 8 July 2019
-@set UPDATED-MONTH July 2019
+@set UPDATED 20 September 2019
+@set UPDATED-MONTH September 2019