apenwarr-redo/t/clean.do

redo example/clean curse/clean deps/clean "space dir/clean"
rm -f c c.c c.c.c c.c.c.b c.c.c.b.b d mode1 makedir.log chdir1 \
	hello [by]ellow *.o *~ .*~ CC LD passfail silence silence.do \
	touch1 touch1.do
rm -rf makedir
Add a new test for filenames with spaces. 2010-11-21 06:18:51 -08:00			`redo example/clean curse/clean deps/clean "space dir/clean"`
$3 and stdout no longer refer to the same file. This is slightly inelegant, as the old style echo foo echo blah chmod a+x $3 doesn't work anymore; the stuff you wrote to stdout didn't end up in $3. You can rewrite it as: exec >$3 echo foo echo blah chmod a+x $3 Anyway, it's better this way, because now we can tell the difference between a zero-length $3 and a nonexistent one. A .do script can thus produce either one and we'll either delete the target or move the empty $3 to replace it, whichever is right. As a bonus, this simplifies our detection of whether you did something weird with overlapping changes to stdout and $3. 2010-12-11 00:29:04 -08:00			`rm -f c c.c c.c.c c.c.c.b c.c.c.b.b d mode1 makedir.log chdir1 \`
			`hello [by]ellow .o ~ .*~ CC LD passfail silence silence.do \`
			`touch1 touch1.do`
			`rm -rf makedir`