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