Re: Bash Reference Manual: broken link

On 4/25/24 2:37 AM, Jim Blackson wrote: Hello GNU, 1. Perhaps there is a broken link in the bread crumb list of the index page of the Bash Reference Manual, found at: https://www.gnu.org/software/bash/manual/html_node/index.html Thanks for the report. I'm not sure if this is an artifact of ho

Re: Bash reference manual: shell parameter expansion examples

On 2/23/24 10:44 AM, James Weigle wrote: Hi! In the Bash reference manual, there are a series of examples of testing if a variable is null or unset: - Under *${parameter:-word}*, the usage is *${var-unset}*. - Under *${parameter:=word}*, the usage is *${var:=DEFAULT}*. - Under *${pa

Re: Bash Reference Manual Type

On Fri, Mar 31, 2023, 3:02 PM Martin Schulte wrote: > Hi Dennis, > > thanks for your answer! > > > This isn't regex. > > Sure! > > > It's a command synopsis using a long standing notation > > style. You can see it set out in POSIX in > > > https://pubs.opengroup.org/onlinepubs/9699919799/basedefs

Re: Bash Reference Manual Type

Date:Fri, 31 Mar 2023 14:41:37 -0400 From:Chet Ramey Message-ID: <625e93f4-280b-2cd4-f84d-2305bd347...@case.edu> | On 3/31/23 12:30 PM, Martin Schulte wrote: | > Hi Chet! | > | >> Thanks for the report. The synopsis should read | >> | >> cd [-L|[-P [-e]]]

Re: Bash Reference Manual Type

On Fri, Mar 31, 2023, 2:47 PM Martin Schulte wrote: > Hi Chet! > > > >> Thanks for the report. The synopsis should read > > >> > > >> cd [-L|[-P [-e]]] [-@] [dir] > > > ^ ^ > > > But aren't these two brackets just superfluous? > > > > -L and -P are mutually exclusive, and -e is va

Re: Bash Reference Manual Type

Hi Chet! > >> Thanks for the report. The synopsis should read > >> > >> cd [-L|[-P [-e]]] [-@] [dir] > > ^ ^ > > But aren't these two brackets just superfluous? > > -L and -P are mutually exclusive, and -e is valid only when -P is > supplied. Yes, my feeling was just that | has s

Re: Bash Reference Manual Type

On 3/31/23 12:30 PM, Martin Schulte wrote: Hi Chet! Thanks for the report. The synopsis should read cd [-L|[-P [-e]]] [-@] [dir] ^ ^ But aren't these two brackets just superfluous? -L and -P are mutually exclusive, and -e is valid only when -P is supplied. -- ``The lyf so s

Re: Bash Reference Manual Type

On Fri, Mar 31, 2023 at 06:30:00PM +0200, Martin Schulte wrote: > Hi Chet! > > > Thanks for the report. The synopsis should read > > > > cd [-L|[-P [-e]]] [-@] [dir] > ^ ^ > But aren't these two brackets just superfluous? Then -L would get the -e too. -- Regards, Mike Jonkmans

Re: Bash Reference Manual Type

Hi Chet! > Thanks for the report. The synopsis should read > > cd [-L|[-P [-e]]] [-@] [dir] ^ ^ But aren't these two brackets just superfluous? Best regards, Martin

Re: Bash Reference Manual Type

On 3/31/23 3:42 AM, Ikenna West wrote: Hello, I was going looking through the Bash reference manual and I noticed that on page 55, when it lists the options for the cd command it is written as cd [-L|[-P [-e]] [-@] [directory]. However, when typing help cd into Bash it prints out cd [-L | [-P

Re: Bash reference manual feedback

On 9/11/22 11:30 AM, David Apps wrote: I hope that you are well. Thank you for your work on this great software. I have some feedback about the document at: http://www.gnu.org/software/bash/manual/bash.html the Bash shell (version 5.1, 21 December 2020). Thanks for your careful reading of th

Re: Bash reference manual feedback

>> 9. It is probably unhelpful to use the "’" character here. > >You have inadvertently stated the entire point of this section: yes, they >are an unhelpful historical anomaly and should not be used in scripts. Of >course this advisory has to actually show the characters that it's telling >you to a

Re: Bash reference manual feedback

I believe you are correct on all points except this one: On Mon, 12 Sept 2022 at 01:30, David Apps wrote: > h3 6.12 Shell Compatibility Mode > > > * the shell does not print a warning message if an attempt is made to > > use a quoted compound assignment as an argument to declare (declare -a > >

Re: Bash reference manual errata

On 2020-07-10 at 09:06 -0400, Chet Ramey wrote: > On 7/10/20 4:24 AM, 홍홍 wrote: > > In Bourne shell > > builtin(https://www.gnu.org/software/bash/manual/bash.html#Bourne-Shell-Builtins > > > > ), > > shift command > > >

Re: Bash reference manual errata

On 7/10/20 4:24 AM, 홍홍 wrote: > In Bourne shell > builtin(https://www.gnu.org/software/bash/manual/bash.html#Bourne-Shell-Builtins > ), > shift command > > > "Parameters represented by the numbers $# to $#-n+1 are unset.

Re: Bash reference manual

Ok, thank you. ⁣Wail Sent from BlueMail ​ On Feb 21, 2019, 16:10, at 16:10, Chet Ramey wrote: >On 2/21/19 6:04 AM, Wail Yahyaoui wrote: >> Hello, >> >> I was reading the Bash reference manual online and I could not find >any mention that when doing variable assignments there should be no >space

Re: Bash reference manual

On 2/21/19 6:04 AM, Wail Yahyaoui wrote: > Hello, > > I was reading the Bash reference manual online and I could not find any > mention that when doing variable assignments there should be no space around > the equal sign. The example in the texinfo manual doesn't include spaces: A variable ma