Re: built-in regex matches wrong character

2018-09-05 Thread Miguel Amat
Thanks for your response Eric, please find my attached screenshot testing both solutions. Seems like setting LC_ALL=C in the environment works fine while 'shopt -s globasciiranges' does not (also I could be testing this the wrong way, first time using shopt). Regards, Miguel On 9/5/18, Eric Blake

Re: built-in regex matches wrong character

2018-09-05 Thread Eric Blake
On 09/05/2018 01:50 PM, mamatb@mamatb-laptop wrote: Description: It seems like bash built-in regex matches some symbols that shouldn't. The following commands shows this: [[ 'º' =~ [o-p] ]] && [[ ! 'º' =~ o ]] && [[ ! 'º' =~ p ]] && echo 'º between o and p but none of t

built-in regex matches wrong character

2018-09-05 Thread mamatb
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/local/share

Re: Bash vi mode's e command (end of word) goes to eol when hitting a unicode character

2018-09-05 Thread Chet Ramey
On 9/3/18 7:13 AM, Enrico Maria De Angelis wrote: > This is kind of a pedantic bug report. > Basically it seems that bash's vi-mode doesn't use the same definition of > words/Words/... that Vim uses (which is the facto the always installed > version of vi), but I write you the same, just in case it