Re: bash can't distinguish between empty and unset arrays

2016-02-03 Thread Stephane Chazelas
2016-02-03 23:43:37 +, Martijn Dekker: > bash treats an empty array as if it were an unset variable, which seems > very illogical as empty is quite distinct from unset: > > $ myarray=() > $ [[ -v myarray ]] && echo set || echo unset > unset [[ -v var ]] is for scalar variables (AFAICT). bash

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Yuri
On 01/31/2016 13:41, Yuri wrote: What makes bash print unicode charater ascii values? I found what the problem is: --disable-nls causes HAVE_ICONV being undefined and \u feature not work. This is a bug, because "nls" refers to translations. I usually turn them off because I don't want t

Re: bash can't distinguish between empty and unset arrays

2016-02-03 Thread Reuti
Hi, Am 04.02.2016 um 00:43 schrieb Martijn Dekker: > bash treats an empty array as if it were an unset variable, which seems > very illogical as empty is quite distinct from unset: > > $ myarray=() > $ [[ -v myarray ]] && echo set || echo unset > unset Which version of bash are you using? > $

bash can't distinguish between empty and unset arrays

2016-02-03 Thread Martijn Dekker
bash treats an empty array as if it were an unset variable, which seems very illogical as empty is quite distinct from unset: $ myarray=() $ [[ -v myarray ]] && echo set || echo unset unset $ set | grep ^myarray= # yet, it's set: myarray=() $ set -u $ for i in "${x[@]}"; do :; done bash: x[@]: un

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Ángel González
Yuri wrote: > On 02/03/2016 14:06, Greg Wooledge wrote: > > Works for me. > > > > wooledg@wooledg:~$ PS1=$'\u2023 \w\$ ' > > ? ~$ > > > > I just can't show it in this cross-system-X2X-with-different- > > character-sets > > setup.  But it works for me, on Debian GNU/Linux with > > LANG=en_US.UTF-8

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Yuri
On 02/03/2016 14:06, Greg Wooledge wrote: Works for me. wooledg@wooledg:~$ PS1=$'\u2023 \w\$ ' ? ~$ I just can't show it in this cross-system-X2X-with-different-character-sets setup. But it works for me, on Debian GNU/Linux with LANG=en_US.UTF-8. I believe you. It does work for you. Just not

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Greg Wooledge
On Wed, Feb 03, 2016 at 01:54:39PM -0800, Yuri wrote: > At least U+2023 is a valid character, it should be printed in utf8 as a > unicode codepoint. My locale is utf8. Works for me. wooledg@wooledg:~$ PS1=$'\u2023 \w\$ ' ? ~$ I just can't show it in this cross-system-X2X-with-different-characte

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Yuri
On 02/03/2016 13:13, Chet Ramey wrote: Sigh. You are mixing two things that perform backslash-escape character processing. If there is no character corresponding to a particular unicode value in the current character set, the escape sequence is left unchanged. So you get through a round of expa

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Chet Ramey
On 2/3/16 3:20 PM, Yuri wrote: > On 01/31/2016 13:41, Yuri wrote: >> I have this line in ~/.bashrc: >> PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] ' > > This link > http://unix.stackexchange.com/questions/25903/awesome-symbols-and-characters-in-a-bash-prompt > says: "Since bash 4.2, you can

Re: bash prints numeric values of unicode characters instead of their UTF8 representations

2016-02-03 Thread Yuri
On 01/31/2016 13:41, Yuri wrote: I have this line in ~/.bashrc: PS1=$'\\[\e[0;38;5;202m\\]\u2514\u2023\\[\e[0m\\] ' This link http://unix.stackexchange.com/questions/25903/awesome-symbols-and-characters-in-a-bash-prompt says: "Since bash 4.2, you can use \u followed by 4 hexadecimal digits