Re: Another redisplay issue in single-byte locales

On 8/13/24 10:23 PM, Grisha Levit wrote: In a single-byte locale, if the prompt is wider than the screen width and contains invisible characters on the last line, and the input line is also wider than the screen width, redisplay gets messed up: Thanks for the report. The code that handled this

[bug #66412] Missing space in documentation

URL: Summary: Missing space in documentation Group: The GNU Bourne-Again SHell Submitter: None Submitted: Wed 06 Nov 2024 09:23:39 AM UTC Category: None Severi

Re: This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo ${#foo[@]}

On Thu, Nov 07, 2024 at 02:38:05 +, David Linden wrote: > Description: > This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo > ${#foo[@]} > How am I supposed to determine that a declared associative array is > empty? The easiest way would be to ensure that the array

This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo ${#foo[@]}

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-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'

RE: [EXTERNAL] - Re: This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo ${#foo[@]}

Thanks, and for the quick reply. Language lawyers... I'm curious what motivated the change. Naively it seems creating a placeholder for a potential future array keeping track of attributes is more work than just creating an empty array. The change is "surprising" to a user, at least this use