Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'
-DPAC
On Sun, Sep 25, 2022 at 03:44:35AM +0700, Robert Elz wrote:
> (in this message, \s represents a space, just for clarity - \s meaning space
> cannot be used in shells, any of them, anywhere)
Just for the record, if \s appears in the regex on the right hand side
of =~ in bash's [[ $string =~ $regex
Date:Sat, 24 Sep 2022 11:21:53 -0500
From:Dennis Williamson
Message-ID:
|If IFS is unset, or its value is exactly , the
| default, then any sequence of IFS characters serves to delimit words.
|If IFS has a value other than the default, then
Thanks for the clarification.
So 'ignoring whitespace' preceeds 'delimiter-logic' in the case of a single
.
I compared the read and readarray sections and did not have a look at Word
Splitting.
Sorry to bother.
Am Samstag, dem 24.09.2022 um 11:21 -0500 schrieb Dennis Williamson:
>
>
> On S
On Sat, Sep 24, 2022 at 11:02 AM kurt wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto
> -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=f
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
-Wall
uname output: Linux kurt-OptiPlex-7
