Re: [PATCH] lib/readline/doc makefiles clean targets

On 11/4/24 9:44 AM, Mike Jonkmans wrote: According to info (make)Standard Targets, we should have: mostlyclean < clean < distclean < maintainer-clean That hierarchy isn't gospel. Agreed, but... The current Makefile rules are fine. There are some issues though. Some less important. 1)

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

there is still code fault $n is supposed to be 'assoc' im sorry bye On Thu, Nov 7, 2024, 23:44 #!microsuxx wrote: > sorry code cleaned up : it was more and stuff > > c() { > eval -- "$@" > l > } > > l() { > r [[ -v $n ]] > r "(( \${#$n[@]} ))" > } > > r() { > eval "$@" && > echo -e "$@\t\t$

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

sorry code cleaned up : it was more and stuff c() { eval -- "$@" l } l() { r [[ -v $n ]] r "(( \${#$n[@]} ))" } r() { eval "$@" && echo -e "$@\t\t$r" } c unset -v assoc c declare -A assoc c 'assoc+=( foo bar )' c 'assoc+=( 2foo 2bar )' c unset -v assoc On Thu, Nov 7, 2024, 23:36 #!micro

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

On Thu, Nov 7, 2024, 23:36 #!microsuxx wrote: > > > On Thu, Nov 7, 2024, 21:10 Chet Ramey wrote: > >> On 11/6/24 9:38 PM, David Linden wrote: >> >> > Bash Version: 4.4 >> > Patch Level: 20 >> > Release Status: release >> > >> > Description: >> > This errors in 4.4, did not in 4.2: set -u;

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

On Thu, Nov 7, 2024, 21:10 Chet Ramey wrote: > On 11/6/24 9:38 PM, David Linden wrote: > > > Bash Version: 4.4 > > Patch Level: 20 > > Release Status: release > > > > Description: > > This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo > ${#foo[@]} > > Yes, this was a bug in ba

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

On 11/6/24 9:38 PM, David Linden wrote: Bash Version: 4.4 Patch Level: 20 Release Status: release Description: This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo ${#foo[@]} Yes, this was a bug in bash-4.2, fixed in bash-4.3. A variable isn't set until it's been assigned

Re: fg via keybind modifies tty settings

On 11/5/24 1:21 AM, David Moberg wrote: Den ons 16 okt. 2024 17:43Chet Ramey > skrev: On 10/13/24 12:10 PM, David Moberg wrote: > A new issue popped up with these changes. After second time of suspend and > foreground with binding, the tty will no

Re: Bash 5.2: broken built-in printf for float numbers

On 11/7/24 4:16 AM, Thomas Dreibholz wrote: Hi, Bash 5.2 has a broken built-in printf for float numbers. https://lists.gnu.org/archive/html/bug-bash/2024-09/msg00094.html -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates C

Re: Bash 5.2: broken built-in printf for float numbers

On Thu, Nov 07, 2024 at 10:16:46 +0100, Thomas Dreibholz wrote: > Hi, > > Bash 5.2 has a broken built-in printf for float numbers. > > Example: printf "%5.1f" 1024 should print "1024.0" (with standard locale > LC_ALL=C.UTF-8) > > Testing the Bash shell in different versions of recent Debian and

Bash 5.2: broken built-in printf for float numbers

Hi, Bash 5.2 has a broken built-in printf for float numbers. Example: printf "%5.1f" 1024 should print "1024.0" (with standard locale LC_ALL=C.UTF-8) Testing the Bash shell in different versions of recent Debian and Ubuntu setups, the output is wrong. Bug tracker for Debian: https://bugs.de

"complete -o filenames" sometimes not working

See the following reproduce example: $ cat ssh_compspec COMP_WORDBREAKS=${COMP_WORDBREAKS//[=:]/} function _ssh() { local cur="$2" pre="$3" local options=( ProxyCommand='/usr/bin/nc -x host:port %h %p -X 5' ProxyCommand='/usr/bin/nc -x host:port %h %p -X connect' C

AW: Re: AW: Re: AW: Re: AW: Re: read command sometimes misses newline on timeout

I can confirm that the patch resolves all the issues I had. Thank you very much for your help, it is very appreciated. On 10/15/24 11:08 AM, Thomas Oettli wrote: > Got it, I just backported your patch to Bash 5.2 and it fixed the issue on > my build host. > I will roll out the patched version to a