declare builtin changes to reject -i when used with -n; readline changes to make control characters visible in search strings; readline signal handling changes to avoid data corruption and UAF; documentation updates for more consistent quoting

2026-07-10 05:30:49 +02:00 · 2025-09-04 12:29:57 -04:00
parent ab17ddb7af
commit a451bfc3f5
46 changed files with 36912 additions and 1499 deletions
@@ -5,7 +5,7 @@
 .\"	Case Western Reserve University
 .\"	chet.ramey@case.edu
 .\"
-.\"	Last Change: Wed Jul 30 14:47:58 EDT 2025
+.\"	Last Change: Mon Aug 25 11:35:58 EDT 2025
 .\"
 .\" For bash_builtins, strip all but "SHELL BUILTIN COMMANDS" section
 .\" For rbash, strip all but "RESTRICTED SHELL" section
@@ -21,7 +21,7 @@
 .ds zY \" empty
 .if \n(zZ=1 .ig zZ
 .if \n(zY=1 .ig zY
-.TH BASH 1 "2025 July 30" "GNU Bash 5.3"
+.TH BASH 1 "2025 August 25" "GNU Bash 5.3"
 .\"
 .ie \n(.g \{\
 .ds ' \(aq
@@ -4938,9 +4938,9 @@ This allows
 here-documents within shell scripts to be indented in a
 natural fashion.
 .PP
-If the delimiter is not quoted, the
+If the delimiter is not quoted, the shell treats the
 .B \e<newline>
-sequence is treated as a line continuation: the two lines are joined
+sequence as a line continuation: the two lines are joined
 and the backslash-newline is removed.
 This happens while reading the here-document, before the check for
 the ending delimiter, so joined lines can form the end delimiter.
@@ -8368,6 +8368,32 @@ standard output.
 Backslash will escape a newline, if necessary.
 These are added to the set of possible completions.
 .PP
+External commands that are invoked to generate completions (
+.Q "external completers" )
+receive the word preceding the completion word as an argument,
+as described above.
+This provides context that is sometimes useful, but may include  
+information that is considered sensitive or part of a word expansion
+that will not appear in the command line after expansion.
+That word may be visible in process listings or in audit logs.
+This may be a concern to users and completion specification authors
+if there is sensitive information on the command line before
+expansion, since completion takes place before words are expanded.
+If this is an issue, completion authors should use functions as
+wrappers around external commands and pass context information to the
+external command in a different way.
+External completers can infer context from the
+.SM
+.B COMP_LINE
+and
+.SM
+.B COMP_POINT
+environment variables, but they need to ensure
+they break words in the same way \fBreadline\fP does, using the
+.SM
+.B COMP_WORDBREAKS
+variable.
+.PP
 After generating all of the possible completions,
 \fBbash\fP applies any filter
 specified with the \fB\-X\fP option to the completions in the list.
@@ -3,7 +3,7 @@
 </HEAD>
 <BODY><TABLE WIDTH=100%>
 <TR>
-<TH ALIGN=LEFT width=33%>BASH(1)<TH ALIGN=CENTER width=33%>2025 April 7<TH ALIGN=RIGHT width=33%>BASH(1)
+<TH ALIGN=LEFT width=33%>BASH(1)<TH ALIGN=CENTER width=33%>2025 August 25<TH ALIGN=RIGHT width=33%>BASH(1)
 </TR>
 </TABLE>
 <BR><A HREF="#index">Index</A>
@@ -6785,7 +6785,7 @@ when it is referenced, or when a variable which has been given the
 <I>integer</I> attribute using <B>declare -i</B> is assigned a value.
 A null value evaluates to 0.
 A shell variable need not have its <I>integer</I> attribute
-turned on to be used in an expression.
+enabled to be used in an expression.
 <P>

 Integer constants follow the C language definition, without suffixes or
@@ -8770,6 +8770,10 @@ Type

 at a <B>bash</B> prompt to see your current terminal settings,
 including the special control characters (usually <B>cchars</B>).
+This binding takes place on each call to <B>readline</B>,
+so changes made by
+
+can take effect.
 <DT><B>blink-matching-paren (Off)</B>

 <DD>
@@ -10528,6 +10532,36 @@ Backslash will escape a newline, if necessary.
 These are added to the set of possible completions.
 <P>

+External commands that are invoked to generate completions (
+
+receive the word preceding the completion word as an argument,
+as described above.
+This provides context that is sometimes useful, but may include  
+information that is considered sensitive or part of a word expansion
+that will not appear in the command line after expansion.
+That word may be visible in process listings or in audit logs.
+This may be a concern to users and completion specification authors
+if there is sensitive information on the command line before
+expansion, since completion takes place before words are expanded.
+If this is an issue, completion authors should use functions as
+wrappers around external commands and pass context information to the
+external command in a different way.
+External completers can infer context from the
+<FONT SIZE=-1><B>COMP_LINE</B>
+
+</FONT>
+and
+<FONT SIZE=-1><B>COMP_POINT</B>
+
+</FONT>
+environment variables, but they need to ensure
+they break words in the same way <B>readline</B> does, using the
+<FONT SIZE=-1><B>COMP_WORDBREAKS</B>
+
+</FONT>
+variable.
+<P>
+
 After generating all of the possible completions,
 <B>bash</B> applies any filter
 specified with the <B>-X</B> option to the completions in the list.
@@ -11629,6 +11663,7 @@ if <I>dir</I> is not supplied, the value of the

 </FONT>
 shell variable is used as <I>dir</I>.
+If <I>dir</I> is the empty string, <B>cd</B> treats it as an error.
 The variable
 <FONT SIZE=-1><B>CDPATH</B>

@@ -16821,7 +16856,7 @@ Array variables may not (yet) be exported.
 <HR>
 <TABLE WIDTH=100%>
 <TR>
-<TH ALIGN=LEFT width=33%>GNU Bash 5.3<TH ALIGN=CENTER width=33%>2025 April 7<TH ALIGN=RIGHT width=33%>BASH(1)
+<TH ALIGN=LEFT width=33%>GNU Bash 5.3<TH ALIGN=CENTER width=33%>2025 August 25<TH ALIGN=RIGHT width=33%>BASH(1)
 </TR>
 </TABLE>
 <HR>
@@ -16930,7 +16965,7 @@ Array variables may not (yet) be exported.
 <DT><A HREF="#lbDJ">BUGS</A><DD>
 </DL>
 <HR>
-This document was created by man2html from /usr/local/src/bash/bash-20250502/doc/bash.1.<BR>
-Time: 04 May 2025 17:25:09 EDT
+This document was created by man2html from /usr/local/src/bash/bash-20250822/doc/bash.1.<BR>
+Time: 25 August 2025 11:45:48 EDT
 </BODY>
 </HTML>
@@ -10351,6 +10351,22 @@ of completions, one per line, to the standard output.  Backslash will
 escape a newline, if necessary.  These are added to the set of possible
 completions.

+   External commands that are invoked to generate completions ("external
+completers") receive the word preceding the completion word as an
+argument, as described above.  This provides context that is sometimes
+useful, but may include information that is considered sensitive or part
+of a word expansion that will not appear in the command line after
+expansion.  That word may be visible in process listings or in audit
+logs.  This may be a concern to users and completion specification
+authors if there is sensitive information on the command line before
+expansion, since completion takes place before words are expanded.  If
+this is an issue, completion authors should use functions as wrappers
+around external commands and pass context information to the external
+command in a different way.  External completers can infer context from
+the COMP_LINE and COMP_POINT environment variables, but they need to
+ensure they break words in the same way Readline does, using the
+COMP_WORDBREAKS variable.
+
   After generating all of the possible completions, Bash applies any
 filter specified with the ‘-X’ option to the completions in the list.
 The filter is a pattern as used for pathname expansion; a ‘&’ in the
@@ -13724,33 +13740,33 @@ Node: Keyboard Macros454096
 Node: Miscellaneous Commands454797
 Node: Readline vi Mode461364
 Node: Programmable Completion462341
-Node: Programmable Completion Builtins471078
-Node: A Programmable Completion Example482815
-Node: Using History Interactively488160
-Node: Bash History Facilities488841
-Node: Bash History Builtins492576
-Node: History Interaction499047
-Node: Event Designators503997
-Node: Word Designators505575
-Node: Modifiers507967
-Node: Installing Bash509904
-Node: Basic Installation511020
-Node: Compilers and Options514896
-Node: Compiling For Multiple Architectures515646
-Node: Installation Names517399
-Node: Specifying the System Type519633
-Node: Sharing Defaults520379
-Node: Operation Controls521093
-Node: Optional Features522112
-Node: Reporting Bugs534835
-Node: Major Differences From The Bourne Shell536192
-Node: GNU Free Documentation License557619
-Node: Indexes582796
-Node: Builtin Index583247
-Node: Reserved Word Index590345
-Node: Variable Index592790
-Node: Function Index610203
-Node: Concept Index624198
+Node: Programmable Completion Builtins472077
+Node: A Programmable Completion Example483814
+Node: Using History Interactively489159
+Node: Bash History Facilities489840
+Node: Bash History Builtins493575
+Node: History Interaction500046
+Node: Event Designators504996
+Node: Word Designators506574
+Node: Modifiers508966
+Node: Installing Bash510903
+Node: Basic Installation512019
+Node: Compilers and Options515895
+Node: Compiling For Multiple Architectures516645
+Node: Installation Names518398
+Node: Specifying the System Type520632
+Node: Sharing Defaults521378
+Node: Operation Controls522092
+Node: Optional Features523111
+Node: Reporting Bugs535834
+Node: Major Differences From The Bourne Shell537191
+Node: GNU Free Documentation License558618
+Node: Indexes583795
+Node: Builtin Index584246
+Node: Reserved Word Index591344
+Node: Variable Index593789
+Node: Function Index611202
+Node: Concept Index625197

 End Tag Table

@@ -56,6 +56,6 @@
 \entry{suspend}{128}{\code {suspend}}
 \entry{compgen}{161}{\code {compgen}}
 \entry{complete}{161}{\code {complete}}
-\entry{compopt}{164}{\code {compopt}}
+\entry{compopt}{165}{\code {compopt}}
 \entry{fc}{169}{\code {fc}}
 \entry{history}{169}{\code {history}}
@@ -17,7 +17,7 @@
 \entry{\code {command}}{63}
 \entry{\code {compgen}}{161}
 \entry{\code {complete}}{161}
-\entry{\code {compopt}}{164}
+\entry{\code {compopt}}{165}
 \entry{\code {continue}}{54}
 \initial {D}
 \entry{\code {declare}}{64}
@@ -4,9 +4,9 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 <!-- This text is a brief description of the features that are present in
-the Bash shell (version 5.3, 18 May 2025).
+the Bash shell (version 5.3, 7 August 2025).

-This is Edition 5.3, last updated 18 May 2025,
+This is Edition 5.3, last updated 7 August 2025,
 of The GNU Bash Reference Manual,
 for Bash, Version 5.3.

@@ -77,10 +77,10 @@ Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Previou
 <h1 class="top" id="Bash-Features-1"><span>Bash Features<a class="copiable-link" href="#Bash-Features-1"> &para;</a></span></h1>

 <p>This text is a brief description of the features that are present in
-the Bash shell (version 5.3, 18 May 2025).
+the Bash shell (version 5.3, 7 August 2025).
 The Bash home page is <a class="url" href="http://www.gnu.org/software/bash/">http://www.gnu.org/software/bash/</a>.
 </p>
-<p>This is Edition 5.3, last updated 18 May 2025,
+<p>This is Edition 5.3, last updated 7 August 2025,
 of <cite class="cite">The GNU Bash Reference Manual</cite>,
 for <code class="code">Bash</code>, Version 5.3.
 </p>
@@ -4434,7 +4434,7 @@ parameter $? (see <a class="pxref" href="#Special-Parameters">Special Parameters
 <p>Bash itself returns the exit status of the last command
 executed, unless a syntax error occurs, in which case it exits
 with a non-zero value.
-See also the <code class="code">exit</code> builtin command (see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a>.
+See also the <code class="code">exit</code> builtin command (see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a>).
 </p>
 <hr>
 </div>
@@ -4457,7 +4457,7 @@ If job control is in effect (see <a class="pxref" href="#Job-Control">Job Contro
 ignores <code class="code">SIGTTIN</code>, <code class="code">SIGTTOU</code>, and <code class="code">SIGTSTP</code>.
 </p>
 <p>The <code class="code">trap</code> builtin modifies the shell&rsquo;s signal handling, as
-described below (see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a>.
+described below (see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a>).
 </p>
 <p>Non-builtin commands Bash executes have signal handlers set to the
 values inherited by the shell from its parent,
@@ -4758,6 +4758,7 @@ cd -P [-e] [-@] [<var class="var">directory</var>]
 <p>Change the current working directory to <var class="var">directory</var>.
 If <var class="var">directory</var> is not supplied, the value of the <code class="env">HOME</code>
 shell variable is used as <var class="var">directory</var>.
+If <var class="var">directory</var> is the empty string, <code class="code">cd</code> treats it as an error.
 If the shell variable
 <code class="env">CDPATH</code> exists,
 and <var class="var">directory</var> does not begin with a slash,
@@ -7252,7 +7253,7 @@ performing filename expansion.
 <dt><code class="code">nocasematch</code></dt>
 <dd><p>If set, Bash matches patterns in a case-insensitive fashion when
 performing matching while executing <code class="code">case</code> or <code class="code">[[</code>
-conditional commands (see <a class="pxref" href="#Conditional-Constructs">Conditional Constructs</a>,
+conditional commands (see <a class="pxref" href="#Conditional-Constructs">Conditional Constructs</a>),
 when performing pattern substitution word expansions,
 or when filtering possible completions as part of programmable completion.
 </p>
@@ -8413,7 +8414,7 @@ subsequently reset.
 <dt><a id="index-READLINE_005fARGUMENT"></a><span><code class="code">READLINE_ARGUMENT</code><a class="copiable-link" href="#index-READLINE_005fARGUMENT"> &para;</a></span></dt>
 <dd><p>Any numeric argument given to a Readline
 command that was defined using
-&lsquo;<samp class="samp">bind -x</samp>&rsquo; (see <a class="pxref" href="#Bash-Builtins">Bash Builtin Commands</a>
+&lsquo;<samp class="samp">bind -x</samp>&rsquo; (see <a class="pxref" href="#Bash-Builtins">Bash Builtin Commands</a>)
 when it was invoked.
 </p>
 </dd>
@@ -9465,7 +9466,7 @@ by name in an expression.
 when it is referenced, or when a variable which has been given the  
 <code class="code">integer</code> attribute using &lsquo;<samp class="samp">declare -i</samp>&rsquo; is assigned a value.
 A null value evaluates to 0.
-A shell variable need not have its <code class="code">integer</code> attribute turned on
+A shell variable need not have its <code class="code">integer</code> attribute enabled
 to be used in an expression.
 </p>
 <p>Integer constants follow the C language definition, without suffixes or
@@ -10219,7 +10220,7 @@ startup files.

 </li><li> Bash reads and executes the <small class="sc">POSIX</small> startup files
 (<code class="env">$ENV</code>) rather than
-the normal Bash files (see <a class="pxref" href="#Bash-Startup-Files">Bash Startup Files</a>.
+the normal Bash files (see <a class="pxref" href="#Bash-Startup-Files">Bash Startup Files</a>).

 </li><li> Alias expansion is always enabled, even in non-interactive shells.

@@ -11724,6 +11725,10 @@ Readline equivalents.
 These override the default Readline bindings described here.
 Type &lsquo;<samp class="samp">stty -a</samp>&rsquo; at a Bash prompt to see your current terminal settings,
 including the special control characters (usually <code class="code">cchars</code>).
+This binding takes place on each call to <code class="code">readline()</code>,
+so changes made by
+&lsquo;<samp class="samp">stty</samp>&rsquo;
+can take effect.
 </p>
 </dd>
 <dt><a id="index-blink_002dmatching_002dparen"></a><span><code class="code">blink-matching-paren</code><a class="copiable-link" href="#index-blink_002dmatching_002dparen"> &para;</a></span></dt>
@@ -13643,6 +13648,25 @@ the standard output.
 Backslash will escape a newline, if necessary.
 These are added to the set of possible completions.
 </p>
+<p>External commands that are invoked to generate completions
+(&quot;external completers&quot;)
+receive the word preceding the completion word as an argument,
+as described above.
+This provides context that is sometimes useful, but may include
+information that is considered sensitive or part of a word expansion
+that will not appear in the command line after expansion.
+That word may be visible in process listings or in audit logs.
+This may be a concern to users and completion specification authors
+if there is sensitive information on the command line before
+expansion, since completion takes place before words are expanded.
+If this is an issue, completion authors should use functions as
+wrappers around external commands and pass context information to the
+external command in a different way.
+External completers can infer context from the <var class="var">COMP_LINE</var>
+and <var class="var">COMP_POINT</var> environment variables, but they need to ensure
+they break words in the same way Readline does, using the
+<var class="var">COMP_WORDBREAKS</var> variable.
+</p>
 <p>After generating all of the possible completions,
 Bash applies any filter
 specified with the <samp class="option">-X</samp> option to the completions in the list.
@@ -15266,10 +15290,17 @@ which this should be turned off, and <code class="code">configure</code> disable
 option automatically for a number of systems.
 </p>
 </dd>
-<dt><code class="code">--with-curses</code></dt>
-<dd><p>Use the curses library instead of the termcap library.
+<dt><code class="code">--with-curses[=<var class="var">LIBNAME</var>]</code></dt>
+<dd><p>Use the curses library instead of the termcap library as the library
+where the linker can find the termcap functions.
 <code class="code">configure</code> usually chooses this automatically, since most systems
 include the termcap functions in the curses library.
+If <var class="var">LIBNAME</var> is supplied, <code class="code">configure</code> does not search for an
+appropriate library and uses <var class="var">LIBNAME</var> instead.
+<var class="var">LIBNAME</var> should be either an argument for the linker
+(e.g., <samp class="option">-l<var class="var">libname</var></samp>)
+or a filename
+(e.g., <samp class="file">/opt/local/lib/libncursesw.so</samp>).
 </p>
 </dd>
 <dt><code class="code">--with-gnu-malloc</code></dt>
@@ -15935,7 +15966,7 @@ command, and what the zeroth argument to the command is to be
 using <code class="code">export -f</code> (see <a class="pxref" href="#Shell-Functions">Shell Functions</a>).

 </li><li>The Bash <code class="code">export</code> and <code class="code">readonly</code> builtins
-(see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a> can
+(see <a class="pxref" href="#Bourne-Shell-Builtins">Bourne Shell Builtins</a>) can
 take a <samp class="option">-f</samp> option to act on shell functions, a <samp class="option">-p</samp> option to
 display variables with various attributes set in a format that can be
 used as shell input, a <samp class="option">-n</samp> option to remove various variable
@@ -10352,6 +10352,22 @@ of completions, one per line, to the standard output.  Backslash will
 escape a newline, if necessary.  These are added to the set of possible
 completions.

+   External commands that are invoked to generate completions ("external
+completers") receive the word preceding the completion word as an
+argument, as described above.  This provides context that is sometimes
+useful, but may include information that is considered sensitive or part
+of a word expansion that will not appear in the command line after
+expansion.  That word may be visible in process listings or in audit
+logs.  This may be a concern to users and completion specification
+authors if there is sensitive information on the command line before
+expansion, since completion takes place before words are expanded.  If
+this is an issue, completion authors should use functions as wrappers
+around external commands and pass context information to the external
+command in a different way.  External completers can infer context from
+the COMP_LINE and COMP_POINT environment variables, but they need to
+ensure they break words in the same way Readline does, using the
+COMP_WORDBREAKS variable.
+
   After generating all of the possible completions, Bash applies any
 filter specified with the ‘-X’ option to the completions in the list.
 The filter is a pattern as used for pathname expansion; a ‘&’ in the
@@ -13725,33 +13741,33 @@ Node: Keyboard Macros454402
 Node: Miscellaneous Commands455106
 Node: Readline vi Mode461676
 Node: Programmable Completion462656
-Node: Programmable Completion Builtins471396
-Node: A Programmable Completion Example483136
-Node: Using History Interactively488484
-Node: Bash History Facilities489168
-Node: Bash History Builtins492906
-Node: History Interaction499380
-Node: Event Designators504333
-Node: Word Designators505914
-Node: Modifiers508309
-Node: Installing Bash510249
-Node: Basic Installation511368
-Node: Compilers and Options515247
-Node: Compiling For Multiple Architectures516000
-Node: Installation Names517756
-Node: Specifying the System Type519993
-Node: Sharing Defaults520742
-Node: Operation Controls521459
-Node: Optional Features522481
-Node: Reporting Bugs535207
-Node: Major Differences From The Bourne Shell536567
-Node: GNU Free Documentation License557997
-Node: Indexes583177
-Node: Builtin Index583631
-Node: Reserved Word Index590732
-Node: Variable Index593180
-Node: Function Index610596
-Node: Concept Index624594
+Node: Programmable Completion Builtins472395
+Node: A Programmable Completion Example484135
+Node: Using History Interactively489483
+Node: Bash History Facilities490167
+Node: Bash History Builtins493905
+Node: History Interaction500379
+Node: Event Designators505332
+Node: Word Designators506913
+Node: Modifiers509308
+Node: Installing Bash511248
+Node: Basic Installation512367
+Node: Compilers and Options516246
+Node: Compiling For Multiple Architectures516999
+Node: Installation Names518755
+Node: Specifying the System Type520992
+Node: Sharing Defaults521741
+Node: Operation Controls522458
+Node: Optional Features523480
+Node: Reporting Bugs536206
+Node: Major Differences From The Bourne Shell537566
+Node: GNU Free Documentation License558996
+Node: Indexes584176
+Node: Builtin Index584630
+Node: Reserved Word Index591731
+Node: Variable Index594179
+Node: Function Index611595
+Node: Concept Index625593

 End Tag Table

@@ -1,11 +1,11 @@
-This is pdfTeX, Version 3.141592653-2.6-1.40.26 (TeX Live 2024/MacPorts 2024.70613_1) (preloaded format=pdfetex 2024.4.9)  30 MAY 2025 08:52
+This is pdfTeX, Version 3.141592653-2.6-1.40.26 (TeX Live 2024/MacPorts 2024.70613_1) (preloaded format=pdfetex 2024.4.9)  25 AUG 2025 11:45
 entering extended mode
 restricted \write18 enabled.
 file:line:error style messages enabled.
 %&-line parsing enabled.
-**\input /usr/local/src/bash/bash-20250529/doc/bashref.texi
-(/usr/local/src/bash/bash-20250529/doc/bashref.texi
-(/usr/local/src/bash/bash-20250529/doc/texinfo.tex
+**\input /usr/local/src/bash/bash-20250822/doc/bashref.texi
+(/usr/local/src/bash/bash-20250822/doc/bashref.texi
+(/usr/local/src/bash/bash-20250822/doc/texinfo.tex
 Loading texinfo [version 2015-11-22.14]:
 \outerhsize=\dimen16
 \outervsize=\dimen17
@@ -161,15 +161,15 @@ This is `epsf.tex' v2.7.4 <14 February 2011>
 texinfo.tex: doing @include of version.texi


-(/usr/local/src/bash/bash-20250529/doc/version.texi) [1{/opt/local/var/db/texmf
+(/usr/local/src/bash/bash-20250822/doc/version.texi) [1{/opt/local/var/db/texmf
 /fonts/map/pdftex/updmap/pdftex.map}] [2]
-(/usr/local/build/bash/bash-20250529/doc/bashref.toc [-1] [-2] [-3]) [-4]
-(/usr/local/build/bash/bash-20250529/doc/bashref.toc)
-(/usr/local/build/bash/bash-20250529/doc/bashref.toc) Chapter 1
+(/usr/local/build/bash/bash-20250822/doc/bashref.toc [-1] [-2] [-3]) [-4]
+(/usr/local/build/bash/bash-20250822/doc/bashref.toc)
+(/usr/local/build/bash/bash-20250822/doc/bashref.toc) Chapter 1
 \openout0 = `bashref.toc'.


-(/usr/local/build/bash/bash-20250529/doc/bashref.aux)
+(/usr/local/build/bash/bash-20250822/doc/bashref.aux)
 \openout1 = `bashref.aux'.

 [1] Chapter 2 [2]
@@ -231,7 +231,7 @@ exlive/fonts/enc/dvips/cm-super/cm-super-t1.enc}] [21] [22] [23] [24]
 [52]
 [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] [67]
 [68] [69] [70] [71] [72] [73]
-Overfull \hbox (38.26585pt too wide) in paragraph at lines 5898--5898
+Overfull \hbox (38.26585pt too wide) in paragraph at lines 5899--5899
 []@texttt set [-abefhkmnptuvxBCEHPT] [-o @textttsl option-name@texttt ] [--] [
 -] [@textttsl ar-gu-ment []@texttt ][] 

@@ -244,7 +244,7 @@ Overfull \hbox (38.26585pt too wide) in paragraph at lines 5898--5898
 .etc.


-Overfull \hbox (38.26585pt too wide) in paragraph at lines 5899--5899
+Overfull \hbox (38.26585pt too wide) in paragraph at lines 5900--5900
 []@texttt set [+abefhkmnptuvxBCEHPT] [+o @textttsl option-name@texttt ] [--] [
 -] [@textttsl ar-gu-ment []@texttt ][] 

@@ -264,9 +264,9 @@ Chapter 7 [124] [125] [126] [127] [128]
 texinfo.tex: doing @include of rluser.texi


-(/usr/local/src/bash/bash-20250529/lib/readline/doc/rluser.texi Chapter 8
+(/usr/local/src/bash/bash-20250822/lib/readline/doc/rluser.texi Chapter 8
 [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139] [140]
-Underfull \hbox (badness 7540) in paragraph at lines 964--970
+Underfull \hbox (badness 7540) in paragraph at lines 968--974
 []@textrm In the ex-am-ple above, @textttsl C-u[] @textrm is bound to the func
 -tion

@@ -279,7 +279,7 @@ Underfull \hbox (badness 7540) in paragraph at lines 964--970
 .etc.


-Underfull \hbox (badness 10000) in paragraph at lines 964--970
+Underfull \hbox (badness 10000) in paragraph at lines 968--974
 @texttt universal-argument[]@textrm , @textttsl M-DEL[] @textrm is bound to th
 e func-tion

@@ -292,7 +292,7 @@ e func-tion
 .etc.

 [141] [142] [143] [144]
-Overfull \hbox (26.43913pt too wide) in paragraph at lines 1210--1210
+Overfull \hbox (26.43913pt too wide) in paragraph at lines 1214--1214
 []@texttt Meta-Control-h: backward-kill-word Text after the function name is i
 gnored[] 

@@ -313,10 +313,10 @@ gnored[]
 texinfo.tex: doing @include of hsuser.texi


-(/usr/local/src/bash/bash-20250529/lib/readline/doc/hsuser.texi Chapter 9
+(/usr/local/src/bash/bash-20250822/lib/readline/doc/hsuser.texi Chapter 9
 [167] [168] [169] [170] [171] [172] [173]) Chapter 10 [174] [175] [176]
 [177] [178]
-Underfull \hbox (badness 10000) in paragraph at lines 10695--10704
+Underfull \hbox (badness 10000) in paragraph at lines 10703--10712
 []@textrm All of the fol-low-ing op-tions ex-cept for `@texttt alt-array-implem
 entation[]@textrm '[],

@@ -329,7 +329,7 @@ entation[]@textrm '[],
 .etc.


-Underfull \hbox (badness 10000) in paragraph at lines 10695--10704
+Underfull \hbox (badness 10000) in paragraph at lines 10703--10712
@textrm `@texttt disabled-builtins[]@textrm '[], `@texttt direxpand-default[]@t
 extrm '[], `@texttt strict-posix-default[]@textrm '[], and

@@ -346,13 +346,13 @@ extrm '[], `@texttt strict-posix-default[]@textrm '[], and
 texinfo.tex: doing @include of fdl.texi


-(/usr/local/src/bash/bash-20250529/doc/fdl.texi [192] [193] [194] [195]
+(/usr/local/src/bash/bash-20250822/doc/fdl.texi [192] [193] [194] [195]
 [196] [197] [198]) Appendix D [199] [200] [201] [202] [203] [204] [205]
 [206] [207] [208] ) 
 Here is how much of TeX's memory you used:
 4116 strings out of 495840
 47662 string characters out of 6171739
- 145154 words of memory out of 5000000
+ 145158 words of memory out of 5000000
 5048 multiletter control sequences out of 15000+600000
 34315 words of font info for 116 fonts, out of 8000000 for 9000
 701 hyphenation exceptions out of 8191
@@ -373,7 +373,7 @@ fonts/type1/public/amsfonts/cm/cmti10.pfb></opt/local/share/texmf-texlive/fonts
 lic/amsfonts/cm/cmtt9.pfb></opt/local/share/texmf-texlive/fonts/type1/public/cm
 -super/sfrm1095.pfb></opt/local/share/texmf-texlive/fonts/type1/public/cm-super
 /sfrm1440.pfb>
-Output written on bashref.pdf (214 pages, 855783 bytes).
+Output written on bashref.pdf (214 pages, 857538 bytes).
 PDF statistics:
 2948 PDF objects out of 2984 (max. 8388607)
 2686 compressed objects within 27 object streams
@@ -317,9 +317,9 @@ The Bourne shell is
 the traditional Unix shell originally written by Stephen Bourne.
 All of the Bourne shell builtin commands are available in Bash, and
 the rules for evaluation and quoting are taken from the @sc{posix}
-specification for the `standard' Unix shell.
+specification for the ``standard'' Unix shell.

-This chapter briefly summarizes the shell's `building blocks':
+This chapter briefly summarizes the shell's ``building blocks'':
 commands, control structures, shell functions, shell @i{parameters},
 shell expansions,
@i{redirections}, which are a way to direct input and output from
@@ -3520,14 +3520,14 @@ and @samp{\} must be used to quote the characters
 however, double quote characters have no special meaning.

 If the redirection operator is @samp{<<-},
-the shell strips leading tab characters are stripped from input lines
+the shell strips leading tab characters from input lines
 and the line containing @var{delimiter}.
 This allows here-documents within shell scripts to be indented in a
 natural fashion.

-If the delimiter is not quoted, the
+If the delimiter is not quoted, the shell treats the
@code{\<newline>}
-sequence is treated as a line continuation: the two lines are joined
+sequence as a line continuation: the two lines are joined
 and the backslash-newline is removed.
 This happens while reading the here-document, before the check for
 the ending delimiter, so joined lines can form the end delimiter.
@@ -9304,11 +9304,11 @@ from a @env{$PATH} search.

@item
 The message printed by the job control code and builtins when a job
-exits with a non-zero status is `Done(status)'.
+exits with a non-zero status is ``Done(status)''.

@item
 The message printed by the job control code and builtins when a job
-is stopped is `Stopped(@var{signame})', where @var{signame} is, for
+is stopped is ``Stopped(@var{signame})'', where @var{signame} is, for
 example, @code{SIGTSTP}.

@item
@@ -10923,7 +10923,7 @@ Once you have determined that a bug actually exists, use the
@code{bashbug} command to submit a bug report or use the form at the
@uref{https://savannah.gnu.org/projects/bash/,Bash project page}.
 If you have a fix, you are encouraged to submit that as well!
-Suggestions and `philosophical' bug reports may be mailed
+Suggestions and ``philosophical'' bug reports may be mailed
 to @email{bug-bash@@gnu.org} or @email{help-bash@@gnu.org}.

 All bug reports should include:
@@ -10937,7 +10937,7 @@ The compiler used to compile Bash.
@item
 A description of the bug behavior.
@item
-A short script or `recipe' which exercises the bug and may be used
+A short script or ``recipe'' which exercises the bug and may be used
 to reproduce it.
@end itemize

@@ -194,12 +194,13 @@ BBAASSHH BBUUIILLTTIINN CCOOMMMMAANNDDSS
       ccdd [--LL] [--@@] [_d_i_r]
       ccdd --PP [--ee] [--@@] [_d_i_r]
              Change the current directory to _d_i_r.  if _d_i_r  is  not  supplied,
-              the  value of the HHOOMMEE shell variable is used as _d_i_r.  The vari-
-              able CCDDPPAATTHH exists, and _d_i_r does not begin with a slash (/),  ccdd
-              uses it as a search path: the shell searches each directory name
-              in  CCDDPPAATTHH  for  _d_i_r.  Alternative directory names in CCDDPPAATTHH are
-              separated by a colon (:).  A null directory name  in  CCDDPPAATTHH  is
-              the same as the current directory, i.e.,
+              the  value of the HHOOMMEE shell variable is used as _d_i_r.  If _d_i_r is
+              the empty string, ccdd treats it as an error.  The variable CCDDPPAATTHH
+              exists, and _d_i_r does not begin with a slash (/), ccdd uses it as a
+              search path: the shell searches each directory  name  in  CCDDPPAATTHH
+              for _d_i_r.  Alternative directory names in CCDDPPAATTHH are separated by
+              a colon (:).  A null directory name in CCDDPPAATTHH is the same as the
+              current directory, i.e.,

              The  --PP option causes ccdd to use the physical directory structure
              by resolving symbolic links while traversing _d_i_r and before pro-