On 2024-12-14 11:36, Chet Ramey wrote:
> On 12/14/24 12:40 PM, Kaz Kylheku wrote:
>> Hi!
>>
>> I first ran into this issue on MacOS using the Homebrew build of Bash 5
>> (BASH_VERSION "5.2.37(1)-release").
>>
>> When a trap is installed for a signal, and delivered, Bash sends characters
>> to the
On 2024-12-14 23:16, Kaz Kylheku wrote:
> The right fix may be to stay away from SIGALRM, since readline
> clearly uses it for something.
Nope! It turns out that by dumb luck, I had picked the
winning signal. The hack used in Basta will not work with
signals other than SIGALRM. (No, not even ones
I'm trying to make sure that my modified version of Bash passes all the
tests, and in the process I'm finding some, erm, oddities.
Firstly, what seems to be a bug:
Looking in tests/printf7.sub it has
INT_MAX=$(getconf INT_MAX 2>/dev/null)
[ -z "$INT_MAX" ] && INT_MAX=2147483647 # assume 3
(see first part for background)
I've patched Bash to merge “shopt” and “set -o”, and now “make tests”
reports some minor differences. I would like some feedback on whether
they're significant enough to warrant fixing.
I've tried to mimic the current behaviour as closely as possible, including
kee
Hi!
I first ran into this issue on MacOS using the Homebrew build of Bash 5
(BASH_VERSION "5.2.37(1)-release").
When a trap is installed for a signal, and delivered, Bash sends characters to
the terminal which move the cursor.
Steps to repro:
1. Register the simplest possible trap for the S
On 12/13/24 6:03 PM, Bug Maybefound wrote:
Bash Version: 5.2
Patch Level: 37
Release Status: release
Description:
If I make a function that does history -s whatever, that seems to be put in
the history instead of the function call rather than along with it.
Yes:
-s Store the arg
On Sun, Dec 15, 2024 at 07:53:44 +0800, HP Prototyping wrote:
> Please find attached the edited file ('user_name' , 'HOSTNAME' , (UU)IDs)
> for privacy concerns.
> I do have a copy of the original file in case some details like a UUID and
> another long ID number would be absolutely necessary for y
On 12/14/24 12:40 PM, Kaz Kylheku wrote:
Hi!
I first ran into this issue on MacOS using the Homebrew build of Bash 5 (BASH_VERSION
"5.2.37(1)-release").
When a trap is installed for a signal, and delivered, Bash sends characters to
the terminal which move the cursor.
It does not; readline d
Dear dale,
Thank you for reaching out.
I did save the output when it first occurred, and it is still occuring at
the moment.
Please find attached the edited file ('user_name' , 'HOSTNAME' , (UU)IDs)
for privacy concerns.
I do have a copy of the original file in case some details like a UUID and
