X-Git-Url: https://git.distorted.org.uk/~mdw/sgt/utils/blobdiff_plain/6f7394991c9610216d1b0a46294dcb71702502e4..f17839e1e0576cac227c12d35945c8fc5c2ea4ba:/buildrun/buildrun.but

diff --git a/buildrun/buildrun.but b/buildrun/buildrun.but
index dca94ee..9b0d118 100644
--- a/buildrun/buildrun.but
+++ b/buildrun/buildrun.but
@@ -136,7 +136,7 @@ behaviour which \cw{buildrun} relies on. Using a directory in
 Of course, instances of \cw{buildrun} using different control
 directories will be completely independent of each other. So you can
 simultaneously run two or more pairs of commands each linked by their
-own pair of \cw{buildrun}s, and as long as each pair has a separaet
+own pair of \cw{buildrun}s, and as long as each pair has a separate
 control directory, they won't interfere with each other.
 
 }
@@ -154,15 +154,15 @@ shell, e.g.
 
 \lcont{
 
-\c buildrun -w sh -c '(cmd1; cmd2 | cmd3) > outfile'
-\e bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
+\c buildrun -w /tmp/ctldir sh -c '(cmd1; cmd2 | cmd3) > outfile'
+\e bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
 
 In \cw{buildrun -r} mode, an alternative to doing that is simply not
 to provide a command at all, and instead tell your shell to run a
 complex command \e{after} \cw{buildrun}, e.g.
 
-\c buildrun -r && (cmd1; cmd2 | cmd3) > outfile
-\e bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
+\c buildrun -r /tmp/ctldir && (cmd1; cmd2 | cmd3) > outfile
+\e bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
 
 (This alternative is not available with \cw{buildrun -w}, since that
 has to run its command as a subprocess so that it can wait for it to