My interactive (using `read`) Bash-script application still suspends
itself after
executing second instance of a player. I've only seen this happen in
the newest development version of Bash.
I tried to debug calls to functions in shtty.c and changes in
attributes made through them but I haven't s
On 11/11/15 6:16 PM, Keith Thompson wrote:
> Yeah, that's fine. I will modify bash to set the original signal
> dispositions to SIG_DFL in interactive shells.
>
>
> Does that mean reverting default_tty_job_signals() in jobs.h to the
> version in bash 4.3.30:
>
> set_signal_handler (
On 11/12/15 5:27 AM, konsolebox wrote:
> My interactive (using `read`) Bash-script application still suspends
> itself after
> executing second instance of a player. I've only seen this happen in
> the newest development version of Bash.
You should be able to attach to the stopped process with gd
I'm coming up with a null-record in my brain when I think
about this: I'd like to be able to record stdout and stderr
without using any temp files into bash array files, AND
record the status of the command executed.
Something along the lines of
Array stderr=() stdout=()
runprog () {
"RUN"
