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

2024-12-19 Thread Chet Ramey
On 12/18/24 4:38 PM, Kaz Kylheku wrote: I understand that Bash will die if you send a SIGUSR1, and it has no trap set up for it; but when it does have a handler set up, it seems that Readline may be blocking the signal (perhaps via the sigprocmask or whatever). I probably won't be digging into i

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

2024-12-19 Thread Chet Ramey
On 12/18/24 4:56 PM, Kaz Kylheku wrote: (That would be an issue if we had used eval: eval 'command ... $$ ...' & now we backgrounded the eval, which then in the background process parses the shell syntax and does all the expanding. Now $$ is the PID of the background process, not that of the

Re: ${| command; } funsub not setting REPLY does not error out with 'set -u' active

2024-12-19 Thread Chet Ramey
On 12/18/24 9:39 PM, Zachary Santer wrote: If one wants to use funsubs that don't expand to anything as a workaround like this, it might be more efficient to use the ${| command; } form, as bash then isn't pointlessly redirecting stdout. The manual describes 'set -u'/'set -o nounset' thusly: Tr

Re: make test errata (part 2)

2024-12-19 Thread Chet Ramey
On 12/14/24 9:35 AM, Martin D Kealey wrote: (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 never did hear why exactly you