forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Generate a basic documentation website with the mkdocs toolkit.

Browse source 
No content yet other than man pages.  To make the man pages render
nicely in mkdocs, I removed the static %-headers and put the code for
them into default.md.tmp.do instead.  That way, the raw input redo-*.md
files will look right in mkdocs.
This commit is contained in:
Avery Pennarun 2018-11-15 23:59:22 -05:00
commit 4cf156e930
18 changed files with 45 additions and 45 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Documentation/redo-whichdo.md
View file

@ -1,7 +1,3 @@
% redo-ifchange(1) Redo %VERSION%
% Avery Pennarun <apenwarr@gmail.com>
% %DATE%
# NAME
redo-whichdo - show redo's search path for a .do file
@ -34,7 +30,7 @@ search path has been exhausted (and printed).
Here's a typical search path for a source file (`x/y/a.b.o`). Because the
filename contains two dots (.), at each level of the hierarchy, `redo` needs
to search `default.b.o.do`, `default.o.do`, and `default.do`.
```sh
$ redo-whichdo x/y/a.b.o; echo $?
x/y/a.b.o.do
@ -47,7 +43,7 @@ to search `default.b.o.do`, `default.o.do`, and `default.do`.
default.b.o.do
default.o.do
0
```
You might use `redo-whichdo` to delegate from one .do script to another,
using code like the following. This gets a little tricky because not only
are you finding a new .do file, but you have `cd` to the .do file