No error for missing semicolon before "then"

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -march=native -ggdb -O2 -pipe uname output: Linux urania 6.6.47-gentoo #1 SMP Mon Aug 19 15:25:50 CEST 2024 x86_64 AMD Ryzen 7 PRO 7730U with Rade

Re: test -v for array does not work as documented

>>>>> On Thu, 20 Feb 2020, Chet Ramey wrote: > On 2/20/20 10:05 AM, Ulrich Mueller wrote: >>>>>>> On Thu, 20 Feb 2020, pepa65 wrote: >> >>> On 20/02/2020 19.48, Ulrich Mueller wrote: >>>> Still, I think it's sad that there is

Re: test -v for array does not work as documented

>>>>> On Thu, 20 Feb 2020, pepa65 wrote: > On 20/02/2020 19.48, Ulrich Mueller wrote: >> Still, I think it's sad that there isn't a command that can test for >> assigned vs void variable, without the need for parsing of declare -p >> output. &g

Re: test -v for array does not work as documented

>>>>> On Wed, 19 Feb 2020, Stephane Chazelas wrote: > 2020-02-19 17:18:14 +0100, Ulrich Mueller: > [...] >> So, is there any syntax that allows to test if a value has been assigned >> to the array variable? Especially, to distinguish VARNAME=() (empty &

Re: test -v for array does not work as documented

>>>>> On Wed, 19 Feb 2020, Chet Ramey wrote: > On 2/19/20 7:00 AM, Ulrich Mueller wrote: >> Bash Version: 5.0 >> Patch Level: 16 >> Release Status: release >> >> Description: >> The GNU Bash Reference Manual Version 5.0 says about test -v: &g

test -v for array does not work as documented

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -march=native -ggdb -O2 -pipe -Wno-parentheses -Wno-format-security uname output: Linux a1i15 4.19.102-gentoo #1 SMP Fri Feb 7 14:32:53 CET 2020

Re: Saving/restoring of posix option unsets expand_aliases

>>>>> On Mon, 25 Nov 2019, Chet Ramey wrote: > On 11/24/19 7:35 AM, Ulrich Mueller wrote: >> Description: >> In a non-interactive non-posix-mode shell, saving the output of >> "shopt -p -o" and restoring it will unset the expand_aliases option.

Saving/restoring of posix option unsets expand_aliases

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -march=native -ggdb -O2 -pipe -Wno-parentheses -Wno-format-security uname output: Linux themis 4.14.154-gentoo #1 SMP Sat Nov 16 15:00:00 CET 2019

Re: bash-4.3: casemod word expansions broken with UTF-8

> On Mon, 16 Nov 2015, Chet Ramey wrote: > Thanks for the report. This was fixed back in January as a result of > this bug report: > http://lists.gnu.org/archive/html/bug-bash/2015-01/msg00091.html > and the fix is in bash-4.4-beta. Please try that and let me know > your results. Indeed,

bash-4.3: casemod word expansions broken with UTF-8

[Resending, apparently my first message didn't make it to the list.] Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_

Re: bash-4.3: casemod word expansions broken with UTF-8

>>>>> On Sun, 15 Nov 2015, Ulrich Mueller wrote: > Description: > In an UTF-8 locale like en_US.UTF-8, the case-modifying > parameter expansions sometimes return invalid UTF-8 encodings. > This seems to happen when the UTF-8 byte sequences that are

bash-4.3: casemod word expansions broken with UTF-8

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/s