commit bash-20190621 snapshot

doc/bash.1

@@ -5,12 +5,12 @@
 .\"	Case Western Reserve University
 .\"	chet.ramey@case.edu
 .\"
-.\"	Last Change: Wed Jun 19 11:22:28 EDT 2019
+.\"	Last Change: Fri Jun 21 10:26:44 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 June 19" "GNU Bash 5.0"
+.TH BASH 1 "2019 June 21" "GNU Bash 5.0"
 .\"
 .\" There's some problem with having a `@'
 .\" in a tagged paragraph with the BSD man macros.
@@ -3546,8 +3546,11 @@ option has been set,
 scans each word for the characters
 .BR * ,
 .BR ? ,
-and
-.BR [ .
+.BR [ ,
+and, under certain circumstances (e.g., when it appears in the expansion of
+an unquoted shell variable, depending on the setting of the \fBposixglob\fP
+shell option),
+.BR \e .
 If one of these characters appears, then the word is
 regarded as a
 .IR pattern ,
@@ -10199,6 +10202,14 @@ files (see
 above)
 to expand to a null string, rather than themselves.
 .TP 8
+.B posixglob
+If set,
+.B bash
+makes words containing unquoted backslashes after expansion eligible for
+pathname expansion, even if they don't contain any other unquoted pattern
+characters. This option is enabled by default, and is enabled when
+\fIposix mode\fP is enabled.
+.TP 8
 .B progcomp
 If set, the programmable completion facilities (see
 \fBProgrammable Completion\fP above) are enabled.