Re: unprintable characters in PS1 different on 5.0.3 vs. 5.0.18?

On 2/7/21 6:04 PM, Chet Ramey wrote: On 2/7/21 11:51 AM, n952162 wrote: Hi, I use this string as my prompt:    $?${boldon}$UCODE\w${boldoff}> where boldon and boldoff are gotten from "tput smso" and "tput rmso". Works fine on my x86_64 boxes at 5.0.18(1) but on my raspberry-pi, at 5.0.3(1), I

Re: unprintable characters in PS1 different on 5.0.3 vs. 5.0.18?

On 2/7/21 11:51 AM, n952162 wrote: Hi, I use this string as my prompt:   $?${boldon}$UCODE\w${boldoff}> where boldon and boldoff are gotten from "tput smso" and "tput rmso". Works fine on my x86_64 boxes at 5.0.18(1) but on my raspberry-pi, at 5.0.3(1), I need to use \[ and \]. You always n

unprintable characters in PS1 different on 5.0.3 vs. 5.0.18?

Hi, I use this string as my prompt:   $?${boldon}$UCODE\w${boldoff}> where boldon and boldoff are gotten from "tput smso" and "tput rmso".  Works fine on my x86_64 boxes at 5.0.18(1) but on my raspberry-pi, at 5.0.3(1), I need to use \[ and \]. Am I not seeing something?

[long] [x-y] bash range wildcard behaviour with non-ASCII data is very random especially with globasciiranges on

Hello, I was wondering why in my en_GB.UTF-8 locale, [0-9] matched "only" on 1044 characters in bash 5.1 while in bash 4.4 it used to match on 1050 different ones. It turns out it's because since 5.0, the globasciiranges option is enabled by default. Then I tried to understand what that option wa