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-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
On 2/3/16 7:54 PM, Yuri wrote:
> 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.
AM_GNU_GETTEXT is the autoconf macro that adds the --disabl
On 2/3/16 6:43 PM, Martijn Dekker wrote:
> 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
If you use the name of an array in a variable context
On 2/3/16 4:54 PM, Yuri wrote:
> And why the same escape character is interpreted in two different ways
> within the same piece of software?
Because $'...' is posix (or soon to be) and standardized and PS1
interpretation is historical bash practice.
--
``The lyf so short, the craft so long to l
hello,
it is no longer existent in the recent devel:
GNU bash, version 4.4.0(3)-rc1 (i686-pc-linux-gnu)
while it is reproducible in the version you file the report for.
sincerely,
pg
On Fri, Feb 5, 2016 at 10:23 AM, wapiflapi wrote:
> Configuration Information [Automatically generated, do
On 02/05/2016 11:13, Chet Ramey wrote:
AM_GNU_GETTEXT is the autoconf macro that adds the --disable-nls option
to configure. It handles checking for iconv by calling AM_ICONV. If
you disable it by calling configure with --disable-nls, it doesn't look
for iconv.
Well, this is wrong in the bash
