Re: Job queing

2006-08-21 Thread Mårten Segerkvist
Having discovering 'trap' I scripted this: declare -a queue[] function q() { [EMAIL PROTECTED]"cd `pwd` && $@" } function runq() { if [ -n "$queue" ]; then local command=$queue queue=("[EMAIL PROTECTED]:1}") bash -c "($command; kill -33 $$)" & fi } trap 'runq' 33 which works almost a

Re: Job queing

2006-08-21 Thread Paul Jarc
Mårten Segerkvist <[EMAIL PROTECTED]> wrote: > i. e. being able to split a one-liner like: > > command1 && command2 && command3 > > into several, separate command lines: You can write that one-liner on multiple lines: command1 && command2 && command3 paul __

Re: Job queing

2006-08-21 Thread Bob Proulx
Mårten Segerkvist wrote: > command1 & > %1 && command2 & > %2 && command3 > > (where the second command line awaits the execution of the first etc.) In a script you can grab the process id of the last background job with $!. Then you can wait for that job id. command & wait $! && command2 &