2 @unnumbered Implementation notes
4 Since there are no strict rules about redo behaviour, here are some
5 remarks about @command{goredo}'s one:
9 @item @file{all} target is default
10 @item @file{stdout} is always captured, but no target is created if it
12 @item empty targets are considered always out of date
13 @item @file{.do}'s @file{$3} is relative path to the file in target directory
14 @item @file{.do} search goes up to @file{/} by default, but can be
15 limited with either @env{$REDO_TOP_DIR} environment variable, or by
16 having @file{.redo/top} file in it
17 @item target's completion messages are written after they finish
18 @item executable @file{.do} is run as is, non-executable is run with
20 @item tracing (@option{-x}) can be obviously done only for
21 non-executable @file{.do}
22 @item parallizable build is done only during @command{redo-ifchange} for
23 human convenience: you can globally enable @env{REDO_JOBS}, but
24 still do for example: @code{redo htmls infos index upload}