How difficult would it be to add an optional timeout argument to the
"wait" builtin?
I occasionally run into situations where this functionality is
desirable, more often than I expect, really. And though the last thing
Bash needs is an additional feature, naively it seems like it wouldn't
be too
On 4/19/23 4:55 PM, Grisha Levit wrote:
If an interactive shell line is just a single loop and the body of the loop
consists only of a function name, and the function body is not a list, ^C
does not cause the loop to break as it otherwise would.
Thanks for the report.
This code in wait_for
On 4/20/23 1:53 PM, Dale R. Worley wrote:
How difficult would it be to add an optional timeout argument to the
"wait" builtin?
Try a variant of this.
trap 'echo timeout!' USR1 # choose your fighter
wait_with_timeout()
{
pid=$1
timeout=$2
{ sleep $timeout && kill
On 4/16/23 10:08 PM, Emanuele Torre wrote:
FIGNORE makes bash only ignore filename completion results that end with
one of the specified suffixes and are not exactly equal to the suffix.
Yes. It requires a non-empty prefix and has since I first added it in
January, 1991 (based on an earlier
