anchor.diff:  killed at that point, regardless of how much longer it was planning to
   run.
   
  -Cues can also be created which run only as long as the corresponding
  -controller pad is held down (this is done by passing a true value with
  -the `:held` optional keyword argument when creating the cue). This is
  -often done for intense effects like strobes. Currently, only physical
  -controllers, not the web interface, honor the `:held` flag, since with
  -the web interface only one cell can be clicked at a time. (This will
  -be easy to change if there is demand for it.)
  +[[held-flag]]Cues can also be created which run only as long as the
  +corresponding controller pad is held down (this is done by passing a
  +true value with the `:held` optional keyword argument when creating
  +the cue). This is often done for intense effects like strobes.
  +Currently, only physical controllers, not the web interface, honor the
  +`:held` flag, since with the web interface only one cell can be
  +clicked at a time. (This will be easy to change if there is demand for
  +it.)
   
   Cues can also offer pressure sensitivity on controllers which support
   this (like the Ableton Push). For such cues, one or more variable used
  
positive.code: running, and its sparkles can lighten the color which would otherwise
  be present in their fixtures.
  
  |===
  
  [[controlling-cues]]
  Controlling Cues
  
negative.code: add to the show. This is done so that a fresh instance of the effect
  is used each time the cue is triggered, in case the effect is complex
  and maintains its own state. The effect creation function will be
  passed a map containing any <<cue-variables,cue-specific variable bindings>>.
  
  There are a number of optional keyword parameters which can be used to
  modify the cue that is created. A summary of some features are
  