bug-bash@gnu.org

2013-12-15 Thread Martin Kealey
I wrote: > Description: > The value of $? after starting a backgrounded command is inconsistent: > $? is unchanged after starting a sufficiently complex command, but > after starting a simpler command it is set to 0. > From: Chet Ramey > Thanks for the report. The exit status of any asynchronous

feature request: apply parameter expansions to array keys

2013-12-15 Thread Ken Irving
No bug here, but I naively expected the pattern substitution expansion to work on array keys as well as values, e.g.: $ declare -A h $ h[foo]=x h[bar]=y $ # show keys and values: $ printf "\t<%s>\n" "${!h[@]}" "${h[@]}" $ # try to pad keys an

bug-bash@gnu.org

2013-12-15 Thread Chet Ramey
On 12/14/13, 2:08 PM, dethrop...@web.de wrote: >I thought the value was only 0 if the fork/spawn was succesful. Sure, of course. (Posix does not document any other return value, btw.) -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis''