Re: Documentation Error

At 2022-06-08T12:05:06-0500, mcmuffin6o wrote: > In section 3.5.3 Shell Parameter Expansion: > > In the sixth paragraph it correctly states that "Bash tests for a > parameter that is unset *or* null" when you use the colon. It later > attempts to restate this but fails by saying "if the colon is >

Documentation Error

In section 3.5.3 Shell Parameter Expansion: In the sixth paragraph it correctly states that "Bash tests for a parameter that is unset *or* null" when you use the colon. It later attempts to restate this but fails by saying "if the colon is included, the operator tests for both parameter's existenc

Small documentation error

Line 1868 from bashref.texi: - and inhibits brace expansion until the closing @samp{@}}.. + and inhibits brace expansion until the closing @samp{@}}.

Re: Readline documentation error

On 5/25/18 9:50 PM, Jorge Maldonado Ventura wrote: > There is an unnecessary closing parenthesis under /bracketed-paste-begin > ()/ from section 8.4.3 of /Bash Reference Manual/ Thanks for the report. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vi

Documentation error? Readline manual

This error (?) appears on section 8.7 of the /Bash Reference Manual/ under complete command -o filenames. > (like adding a slash to directory names quoting special characters, or suppressing trailing spaces) A comma is needed here. Correction: (like adding a slash to directory names*,* quoting

Readline documentation error

There is an unnecessary closing parenthesis under /bracketed-paste-begin ()/ from section 8.4.3 of /Bash Reference Manual/ diff --git a/lib/readline/doc/rluser.texi b/lib/readline/doc/rluser.texi index 1c9acdc..d42f6f6 100644 --- a/lib/readline/doc/rluser.texi +++ b/lib/readline/doc/rluser.texi @

Re: Documentation error

On 5/18/18 5:09 PM, Jorge Maldonado Ventura wrote: >> After the string is decoded, it is expanded via parameter expansion, > command substitution, arithmetic expansion, and quote removal, subject > to the value of the |promptvars| shell option (see _Bash Builtins_). > > The documentation should po

Documentation error

> After the string is decoded, it is expanded via parameter expansion, command substitution, arithmetic expansion, and quote removal, subject to the value of the |promptvars| shell option (see _Bash Builtins_). The documentation should point to the *The Set Builtin*, which is the section that cove

bash documentation error

Dear Bug-Bash: I found an error in your online bash documentation at [1]http://www.gnu.org/software/bash/manual/bashref.html In the [2]Conditional = Constructions (§3.2.4.2) section under the “case” command , the second paragraph start= s out: Each clau= se must be terminat

Re: documentation error in the FAQs

Elmar Stellnberger <[EMAIL PROTECTED]> writes: > Bash Version: 3.1 > Patch Level: 17 > Release Status: release > concerns: FAQ E4) > > "IFS=." inside a subprocess can not influence the read builtin: > read A B C D < <(IFS=.; echo $(/usr/local/bin/ipaddr)) It is true that is has no effect on read,

documentation error in the FAQs

Bash Version: 3.1 Patch Level: 17 Release Status: release concerns: FAQ E4) "IFS=." inside a subprocess can not influence the read builtin: read A B C D < <(IFS=.; echo $(/usr/local/bin/ipaddr)) should be: IFS="." read A B C D < <(echo $(/usr/local/bin/ipaddr))