[CyberShadow]

Could you please add some usage examples or elaborate on when this tool would be useful? For example,

> building several targets of a Makefile

As opposed to `make && sudo make install` ?

> downloading multiple files one at a time

As opposed to `(wget url1 &) ; (wget url2 &)` ?

> or simply as a glorified `nohup`

As opposed to `nohup` ?

[cozzyd]

I imagine it's useful if you don't know all the commands you want to queue at the beginning.

For example:

    nq ./my_awesome_analysis /data/complicated_file_with_long_name.dat

    # um... what's the next file? 

    ls /data 
    nq ./my_awesome_analysis /data/even_more_complicated_path.dat

    man rsync
    nq rsync -avh --progress out* somewhere_else.net:

[jessaustin]

You don't need nq for that. Just kick off ./my_lame_analysis in the background whenever you want.

[cozzyd]

Yes but then they will execute at the same time instead of sequentially.

[shanemhansen]

How about:

    ./my_awesome_analysis /data/complicated_file_with_long_name.dat &
    # do some stuf
    wait
    ./my_awesome_analysis /data/even_more_complicated_path.dat

[e40]

It's still not equivalent, and it's more cumbersome.

[PeterWhittaker]

Thank you for making the comment I came to make!

The shells have had queueing for, well, a very, very long time....