On 8/29/24 10:22 AM, Andrey Kovalev wrote:
In the loop, when iterating through the array, there was no check whether an
element of the array goes beyond its limits. And with certain input data,
there is an outflow from the array.
Thanks for the report. This was fixed back in May, 2023, the resu
In the loop, when iterating through the array, there was no check whether an
element of the array goes beyond its limits. And with certain input data,
there is an outflow from the array.
---
builtins/printf.def | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtins/printf.de
In the loop, when iterating through the array, there was no check whether an
element of the array goes beyond its limits. And with certain input data,
there is an outflow from the array.
---
builtins/printf.def | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtins/printf.de
Enable prettier-printing of <<# heredocs by printing the body indented
one level further than surrounding text and the final delimiter at the
same indentation level as the surrounding text.
0002-indent-stripping-heredoc-indented-printing.patch
Description: Binary data
Without this patch, Bash can hand out user-visible timestamps
that are out of order, because on GNU/Linux the 'time'
function uses a different clock than file timestamps
and the 'gettimeofday' function.
The out-of-order timestamps can lead to user-confusion.
https://sourceware.org/bugzilla/show_bug
> The TOOL variant will automatically search for a $host prefixed program
> (e.g. x86_64-pc-linux-gnu) rather than looking for `ar` only. This is
> useful when cross-compiling and it matches the behavior of the other
> tools that configure relies on (e.g. cc & ranlib).
Thanks for the fix.
Chet
The TOOL variant will automatically search for a $host prefixed program
(e.g. x86_64-pc-linux-gnu) rather than looking for `ar` only. This is
useful when cross-compiling and it matches the behavior of the other
tools that configure relies on (e.g. cc & ranlib).
Signed-off-by: Mike Frysinger
---
Correctly check for printable characters using wchar_t* and iswprint().
Signed-off-by: Roman Rakus
---
bash-4.2/lib/sh/strtrans.c | 18 ++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/bash-4.2/lib/sh/strtrans.c b/bash-4.2/lib/sh/strtrans.c
index 57f9af0..a31b
Hi Chet,
Bash-3.0 introduced {-2..2} syntax which generates -2, -1, 0, 1, 2.
Unfortunately, it clashes with my extension which doesn't do negative
integers; instead, mine was designed for "equal width" integer, like 00,
01, 02.
Do you plan to keep the negative integer features o
