Hello,
I would like to report an unexpected behavior with array declaration on latest
Bash, which is very likely to be a bug. I discovered this when I found Pinentry
could not display GUI windows properly.
- Bash version: 5.2.26(1)-release
- OS: Arch Linux (Kernel: 6.9.9-arch1-1) (My PC), and T
On Thu, Jul 18, 2024 at 00:00:17 +, Charles Dong via Bug reports for the
GNU Bourne Again SHell wrote:
> - Declare an array: `a=(aa bb cc dd)`
> - Print this array: `echo $a` or `printf $a`
$a is equivalent to ${a[0]}. That's not how you print an entire array.
The easiest way to print an ar
On 7/11/24 3:51 AM, konsolebox wrote:
On Thu, Jul 11, 2024 at 4:08 AM Chet Ramey wrote:
and the BASH_SOURCE
absolute pathname discussion has been bananas, so that's not going in any
time soon.
Maybe just create BASH_SOURCE_REAL instead to avoid the gripes.
I don't think so. It's not very us
On Thu, Jul 18, 2024, at 8:57 AM, Greg Wooledge wrote:
> $a is equivalent to ${a[0]}.
This is documented, by the way. It is not a bug.
"Referencing an array variable without a subscript is equivalent to referencing
with a subscript of 0."
https://www.gnu.org/software/bash/manual/html_node/Arra
On 7/14/24 8:40 PM, Zachary Santer wrote:
On Fri, Jul 5, 2024 at 2:38 PM Chet Ramey wrote:
There is code tagged
for bash-5.4 that allows `wait -n' to look at these exited processes as
long as it's given an explicit set of pid arguments.
I agree with all the knowledgeable people here telling
On Thu, Jul 18, 2024 at 11:02 PM Chet Ramey wrote:
>
> On 7/11/24 3:51 AM, konsolebox wrote:
> > On Thu, Jul 11, 2024 at 4:08 AM Chet Ramey wrote:
> >> and the BASH_SOURCE
> >> absolute pathname discussion has been bananas, so that's not going in any
> >> time soon.
> >
> > Maybe just create BASH
On 7/14/24 8:40 PM, Zachary Santer wrote:
See my attachments, though. Something about my second set of process
substitutions is causing 'wait' without arguments to not wait for the
final procsub, whose pid is still in $! at the time.
There's an easy fix for this, thanks.
It's not in the set o
Hi,
In lib/malloc/malloc.c there is a read that occurs 1 or 2 indexes before
the first element in the buffer. The issue is this macro:
/* Use this when we want to be sure that NB is in bucket NU. */
#define RIGHT_BUCKET(nb, nu) \
(((nb) > binsizes[(nu)-1]) && ((nb) <= binsizes[(nu)]))
Wh
TL;DR: what you are asking for is unsafe, and should never be added to any
published version of any shell.
On Tue, 16 Jul 2024 at 17:47, David Hedlund wrote:
> Do you think that it would be appropriate to submit this feature request
> to the developers of the rm command instead.
>
This suggesti
