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

[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 even ones like SIGBUS; I tried).

It looks as if when Bash is sitting in the call to readline to
edit the command line, it's not able to receive external signals
like SIGUSR1. SIGALRM likely works because readline keeps it
unblocked and handles it.

(Without looking at code, I can only hypothesize that the Bash
trap for ALRM is executed because readline keeps track of the
previous handler and chains to it out of its own handler.
Furthermore, it could be that when readline sees that there /is/
such a prior handler, then in that case it does the thing with the
escape sequences sent to the terminal.)