here's a patch that fixes this problem
$ printf "<%3s><%3b>"
< ><>
---
xoxo iza
From c5ffd55ffa9224dd7919a4d09b27a11308d2152e Mon Sep 17 00:00:00 2001
From: izabera
Date: Sat, 24 Sep 2016 02:01:16 +0200
Subject: [PATCH] fix printf %b without an argument
old behavior:
$ printf "<%3s><%3b>"
<
Reuti wrote:
Am 22.09.2016 um 15:23 schrieb Greg Wooledge :
On Wed, Sep 21, 2016 at 11:15:45PM -0400, mobatu...@yahoo.ca wrote:
declare -a "$string" # results in execution of $string
declare -a a=($string)# does not result in execution of $string
This is why you don't u
On 9/21/16 11:15 PM, mobatu...@yahoo.ca wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
> ___
> You can see in the picture below that:
> declare -a "$ExecuteThisData"
> resulted in executing the string "$Exe
Hello,
I'm using 'GNU bash, version 4.3.46(1)-release (x86_64-suse-linux-gnu)'
provided by OpenSUSE Tumbleweed. I recently faced a problem that, depending
on the system load, bash returns different exit codes. I detected that it
is related to trap processing.
My tests uses 3 blocks of code:
1) in
On 9/22/16 7:13 AM, Norm Abramovitz wrote:
> Bash Version: 4.4
> Patch Level: 0
> Release Status: release
>
> Description:
>
> I was playing around with the new --help feature and I was expecting it
> should work for all commands at the interactive prompt. The local command
> did not work that
On 9/21/16 7:06 PM, Martijn Dekker wrote:
> On bash with --enable-minimal-config, as of version 4.3 (as far as I can
> tell), there appears to be a bug with the exit status on returning from
> subshells. Apparently the exit status of the subshell is not given to
> the main shell.
Thanks for the re
