Hi Jon,
I was going to bug you to add documentation for the --template feature
for forester new, but then I thought it would be slightly more
convenient if I made a stab at it. I'm not sure what release this was
added in.
-Owen
---
trees/jms-011P.tree | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/trees/jms-011P.tree b/trees/jms-011P.tree
index 97b0a7e..f51ed72 100644
--- a/trees/jms-011P.tree
+++ b/trees/jms-011P.tree
@@ -212,3 +212,19 @@ foreign = ["my-public-forest.json"]
\p{One possiblity is to extend HTML with just the hypermedia controls and embedded microformats needed for Forester’s operation. This re-coupling of presentation and data would, paradoxically, facilitate Forester to evolve more rapidly over time while simultaneously increasing the longevity of forests that have been compiled using older versions of the tool.}
}
+\subtree[jms-013F]{
+\title{Templates for \code{forester new}}
+
+\p{The \code{new} subcommand now takes an optional \code{--template} argument. To use this, make a \code{templates} directory in your home directory with trees like \code{templates/definition.tree} containing}
+
+\pre{\verb>|
+\taxon{definition}
+>}
+
+\p{Then \code{forester new --template=definition} will create a tree that looks like}
+
+\pre{\verb>>|
+\date{<today>}
+\taxon{definition}
+>>}
+}
--
2.47.0