Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-14 Thread Kaz Kylheku
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 si

Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-14 Thread Kaz Kylheku
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 eve

Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-18 Thread Kaz Kylheku
On 2024-12-18 13:46, microsuxxor wrote: > try > > p=$$ ; while sleep 1 ; do kill -USR1 "$p" ; done & That's not necessary; my existing repro steps successfully show a difference between two signals, that being the only difference between them. The $$ parameter is expanded to a decimal numeric

Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-18 Thread Kaz Kylheku
On 2024-12-18 06:58, Chet Ramey wrote: >> With signals other than SIGALRM, the code has to be careful; if it >> ever happens that the signal is delivered without the trap being >> in place, Bash will die. > > Same with SIGALRM, too. OK, that is my mistake. These steps do terminate Bash: trap -

Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-18 Thread Kaz Kylheku
On 2024-12-18 12:48, Chet Ramey wrote: > On 12/18/24 1:27 PM, Kaz Kylheku wrote: > >> What remains is the question why I somehow cannot get my >> stuff to work with a different signal like SIGUSR1 or SIGVTALRM. >> >> Bash will not take them while it

Re: Bash spews bracketed-paste escape sequences when handling signal.

2024-12-18 Thread Kaz Kylheku
On 2024-12-18 11:02, microsuxxor wrote: > post ur code for review , if u want .. It's BSD-licensed freeware: https://www.kylheku.com/cgit/basta/about/

Bash spews bracketed-paste escape sequences when handling signal.

2024-12-14 Thread Kaz Kylheku
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

Re: Possible bug for nested curly brace expansion

2025-03-06 Thread Kaz Kylheku
On 2025-03-06 11:58, Lawrence Velázquez wrote: > On Thu, Mar 6, 2025, at 1:48 PM, microsuxx wrote: >> {0} is no expansion >> {0,} is >> it must be 2+ > > And this is documented. It is not a bug. > > A correctly-formed brace expansion must contain unquoted > opening and closing braces

Degenerate case in brace expansion.

2025-03-08 Thread Kaz Kylheku
Hi all, $ echo {a..zz} {a..zz} Right; the sequence is not well-formed according, and so this is not brace syntax; the syntax stays intact as verbatim text, braces and all. But: $ echo {a..{z,y}} a..z a..y Is this documented? I would expect it to produce {a..z} {a..y} on the hypot

Cosmetic issue in job control display of suspsended "command" command.

2025-03-03 Thread Kaz Kylheku
Hi All, Consider this trivial wrapper: wrapper() { command "$@" } Under an older bash like 4.4.20, when we suspend this with Ctrl-Z we get this: $ wrapper cat ^Z [1]+ Stopped cat But under a newer bash, like 5.2.37: $ wrapper cat ^Z [1]+ Stopped command "$