bash-5.0: problem with variable scoping in posix-mode

Configuration Information: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -O0 -fno-omit-frame-pointer -ggdb -pipe -Wno- parentheses -Wno-format-security uname output: Linux gentoo-test 4.14.78-gentoo #1 SMP Wed Oct 24 20:06:13 MSK 2018 x86_64 Westmere E56xx/L56x

Re: case statement: wrong behaviour of the ";;&" operator

On 1/26/19 12:30 AM, Norman Krebs wrote: > Bash Version: 5.0 > Patch Level: 2 > Release Status: release > > Description: > >     "echo x" shouldn't be executed here, but it gets: > >     case "1" in >     1) : ;;& >     2) : ;; >     *) echo x ;; >     esac > >     Following the ma

Re: bash-5.0: problem with variable scoping in posix-mode

On 1/27/19 7:58 AM, Alexander Tsoy wrote: > Bash Version: 5.0 > Patch Level: 2 > Release Status: release > > > Description: > > There is a problem with variable scoping when variable is created from > assignment statement preceding function call in posix-mode. See an > example below. > > > Re

Re: `complete -p -- ` doesn't yield reusable input when "-F" is assigned an invalid identifier

On 1/24/19 12:24 PM, Great Big Dot wrote: > Bash Version: 5.0 > Patch Level: 0 > Release Status: release > > > Description: > According to the manual's section on the `complete` builtin: > > > "If the -p option is supplied, or if no options are supplied, > existing completion spec