Re: bash-5.0: case command bug

On 1/17/19 6:21 PM, Drab Martin wrote: > Hi, > > I have a problem with bash 5.0: > > - > machine1 ~ # bash --version > GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu) > Copyright (C) 2019 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later

bash-5.0: case command bug

Hi, I have a problem with bash 5.0: - machine1 ~ # bash --version GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to c

Re: grammatical error in manual

On 1/16/19 11:17 AM, Robert Swan wrote: > Hello; > > Section 3.5.3 Shell Parameter Expansion in the manual has a repeated phrase in > the ${parameter%word} description, "If the pattern matches If the pattern > matches". Thanks for the report. Chet -- ``The lyf so short, the craft so long to le

Re: Typo in rluser.texi

On 1/16/19 6:55 PM, Jorge wrote: > Line 2047 of lib/readline/doc/rluser.texi > >> apply to completion on the inital non-assignment word on the line, or > after a > > It should say "initial". Thanks for the report. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

Re: [DOC] Incomplete explanation about the regex =~ operator

On 1/17/19 1:53 AM, kevin wrote: > >    Since *[[* isn't a normal command (like [ is), but a /shell >    keyword/, *it has special magical powers*. *It parses its arguments >    before they are expanded by Bash and does the expansion itself*, >    taking the result as a single argument, even if t

Re: [DOC] Incomplete explanation about the regex =~ operator

On Thu, Jan 17, 2019 at 07:53:09AM +0100, kevin wrote: > I looked at Greg Wooledge's site > : > > >Since *[[* isn't a normal command (like [ is), but a /shell >keyword/, *it has spe