Bash-4.4 Official Patch 22

2018-06-01 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.4 Patch-ID: bash44-022 Bug-Reported-by:Nuzhna Pomoshch Bug-Reference-ID: <1317167476.1492079.1495999776...@mail.yahoo.com> Bug-Reference-URL: https://lists.gn

Bash-4.4 Official Patch 23

2018-06-01 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.4 Patch-ID: bash44-023 Bug-Reported-by:Martijn Dekker Bug-Reference-ID: <5326d6b9-2625-1d32-3e6e-ad1d15462...@inlv.org> Bug-Reference-URL: http://lists.gnu.or

Bash-4.4 Official Patch 21

2018-06-01 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.4 Patch-ID: bash44-021 Bug-Reported-by:wer...@suse.de Bug-Reference-ID: <201803281402.w2se2voa000...@noether.suse.de> Bug-Reference-URL: http://lists.gnu.org/a

Bash-4.4 Official Patch 20

2018-06-01 Thread Chet Ramey
BASH PATCH REPORT = Bash-Release: 4.4 Patch-ID: bash44-020 Bug-Reported-by:Graham Northup Bug-Reference-ID: <537530c3-61f0-349b-9de6-fa4e2487f...@clarkson.edu> Bug-Reference-URL: http://lists.gn

Re: case pattern checking with bash -n fails

2018-06-01 Thread Greg Wooledge
On Fri, Jun 01, 2018 at 07:17:29PM +0200, Paul Förster wrote: > file: case-test (700) > ==8<-- > #!/bin/bash > > shopt -s extglob > case "${1}" in > +([[:alpha:]])*([[:alnum:]-_])) > echo "${1} matches" ;; > # ... some more cases here... > *) ech

case pattern checking with bash -n fails

2018-06-01 Thread Paul Förster
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.3 -L/home/abuild/rpmbuild/BUILD/bash-4.3/../readline-6.3 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -D

Re: [PATCH] Add nofirstword completion option

2018-06-01 Thread Luca Boccassi
On Tue, 2018-05-29 at 15:44 +0100, Luca Boccassi wrote: > On Fri, 2018-05-25 at 14:40 -0400, Chet Ramey wrote: > > On 5/25/18 1:42 PM, Luca Boccassi wrote: > > > > > > There is already logic that determines whether the shell is > > > > trying to > > > > complete a command word (in_command_position

Re: Clarify cases of implicit and explicit line continuation

2018-06-01 Thread Chet Ramey
On 6/1/18 1:28 AM, Shriramana Sharma wrote: > Hello. See > https://unix.stackexchange.com/questions/253518/where-are-bash-line-continuations-after-and-documented. > > Roughly put, wherever lines terminating with a particular token are > syntactically valid, they are taken as complete, and an expl

Clarify cases of implicit and explicit line continuation

2018-06-01 Thread Shriramana Sharma
Hello. See https://unix.stackexchange.com/questions/253518/where-are-bash-line-continuations-after-and-documented. Roughly put, wherever lines terminating with a particular token are syntactically valid, they are taken as complete, and an explicit \ is required to continue the line, but lines end