From f17839e1e0576cac227c12d35945c8fc5c2ea4ba Mon Sep 17 00:00:00 2001 From: simon Date: Fri, 9 Nov 2012 18:43:25 +0000 Subject: [PATCH] Minor man page fixes: one typo, and missing control directory arguments in two example command lines. git-svn-id: svn://svn.tartarus.org/sgt/utils@9695 cda61777-01e9-0310-a592-d414129be87e --- buildrun/buildrun.but | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) 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 -- 2.11.0