From ab8e05a1451022035af7eba0cf292a7e20618804 Mon Sep 17 00:00:00 2001 From: Matthew Butterick Date: Thu, 27 Jun 2019 19:44:30 -0700 Subject: [PATCH] note about `setup` before `render -p` --- pollen/private/ts.rktd | 2 +- pollen/scribblings/raco.scrbl | 10 +++++++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/pollen/private/ts.rktd b/pollen/private/ts.rktd index bdfc6f0..ca9403d 100644 --- a/pollen/private/ts.rktd +++ b/pollen/private/ts.rktd @@ -1 +1 @@ -1561571116 +1561689870 diff --git a/pollen/scribblings/raco.scrbl b/pollen/scribblings/raco.scrbl index ff4bf70..8982be3 100644 --- a/pollen/scribblings/raco.scrbl +++ b/pollen/scribblings/raco.scrbl @@ -99,7 +99,15 @@ See also @seclink["raco-pollen-render-poly"]. The optional @exec{--parallel} or @exec{-p} switch creates a set of parallel rendering jobs. On a multi-core machine, this will usually make your rendering job finish faster. The order of rendering is not guaranteed, of course, so if your project depends on a certain order of rendering, don't use this option. @terminal{ -> raco pollen render -p foo.html bar.html zam.css} +> raco pollen render -p foo.html bar.html zam.css +} + +As a rule of thumb, parallel rendering works best if you do @exec{raco setup} first, which updates Pollen's disk caches: + +@terminal{ +> raco setup +> raco pollen render -p +} @italic{Warning}: In all cases, the newly rendered output file will overwrite any previous output file.