\n You have #{(sheep for sheep in flock when sheep.color is 'black').length}\n black sheep in the flock.\n
\n```\n\nIncluding other files is possible thanks to the function `partial`. This works in both Express and the browser.\n\n```html\n\n #{partial \"navigation.toffee\", {username: user.name, age: 22} }\n
\n```\n\nBut the greatest pleasure arises when you enter\n`coffee mode`. Note the `{# ... #}` region, where you can write multiple lines of CoffeeScript.\n\n```html\n\n {# ten_numbers = [1,3,2,4,5,8,6,7,69, Math.random()] ten_numbers.sort (a,b) ->\n b - a #} The largest number I can even think of is #{ten_numbers[0]}.\n
\n```\n\nAgainst all odds, inside `coffee mode`, you can switch back to `toffee mode` with `{: ... :}`. It's endlessly nestable.\n\n```html\n\n You know, #{name} would make a great designated driver. And she only lives\n #{profile.distance}km away. {# if profile.car? {: And wow, she drives a\n #{profile.car.model} :} else {: But, alas, she has no wheels. :} #}\n
\n:} #}\n```\n\n### Partials (including other files), both for output and configuration\n\nIncluding other files in Toffee is easy with the `partial` function, which includes another template file.\n\n```html\nOur site's name is #{site_name}.
\n\n\n{# passback.site_name = \"gittub.com\" #}\n```\n\nFor your naming convenience, you can also use the `load` function, which is identical to `partial` but withholds output.\n\n### Post-processing\n\nNew in the latest version of Toffee, you can pass a `postProcess` function to Toffee. This works for individual partials or even\nan entire document. The `postProcess` function performs a final transformation on your output.\n\nOne smart use of postProcess is to find anything inside triple tick marks and perform a code higlighting.\n\n```html\n{# print partial './something.toffee', { foo: 1000 postProcess: (s) ->\nfind_and_higlight_code_in s } #}\n```\n\nYou could define `find_and_highlight_code_in` anywhere in your publishing stack. You can pass it from your webserver, define it above, whatever. If you're\ndoing this server-side, consider the popular Node module _highlight.js_. In that case, define a highlight function that hunts for\ntriple tick marks and then uses highlight's highlighter to transform it.\n\nYour users shouldn't have to wait for client-side JS to re-process your pages.\n\n### Indentation\n\nSince CoffeeScript is sensitive to indenting, so is Toffee.\n\nBut...Toffee doesn't care where you start your CoffeeScript. When you want to create a coffee block,\nyou can indent it however you like, and all that matters is that the internal,\nrelative indenting is correct. For example, these are identical:\n\n```html\n\n {# if user.is_awesome {: YAY! :} #}\n
\n\n {# if user.is_awesome {: YAY! :} #}\n
\n```\n\nIn other words, feel free to pick whatever indentation baseline you want when entering a region of CoffeeScript.\n\nNote that where you put your toffee mode tokens (`{:`) is important, as the following illustrates:\n\n```html\n\n {# if x is true if y is true if z is true w = true {: x is true! Dunno\n anything about y or z, though. :} #}\n
\n```\n\nWhy? Because this is roughly the same as saying:\n\n```html\n\n {# if x is true if y is true if z is true w = true print \"\\n x is true! Dunno\n anything about y or z, though.\\n \" #}\n
\n```\n\nOne syntactic convenience: if you start a `{:` on the same line as some preceeding CoffeeScript, it's\ntreated the same as putting it on a new line and indenting one level.\nSo the following three conditionals are the same:\n\n```html\n{# if x is true {:yay:} #}\n```\n\n```html\n{# if x is true {:yay:} #}\n```\n\n```html\n{# if x is true {: yay :} #}\n```\n\nThe third example has extra whitespace around the \"yay,\" but otherwise the three are logically identical.\n\n### One gotcha with indenting\n\nTHIS IS AN ERROR\n\n```html\n{# if x is 0 {:Yay!:} else {:Burned:} #}\n```\n\nNote that the indentations before the 'if' and the 'else' are technically different,\nas the `if` has only 1 space before it, and the `else` has 2. This is better style anyway:\n\nGOOD\n\n```html\n{# if x is 0 {:Yay!:} else {:Burned:} #}\n```\n\nWith a single line of CoffeeScript, feel free to keep it all on one line:\n\nGOOD\n\n```html\nAn ode to Ruby on Rails
\n#{partial 'ode.toffee'}
\n ##}\n#{danger_code}
\n```\n\nYou can control the escaping, but here are the defaults:\n\n- if it's a string or scalar, it is escaped for HTML safety.\n- it's an array or object, it is converted to JSON.\n\n### Custom Escaping\n\nYou can bypass the above rules.\n\n- `#{json foo}`: this outputs foo as JSON.\n- `#{raw foo}`: this outputs foo in raw text.\n- `#{html foo}`: this outputs foo, escaped as HTML. For a scalar, it's the same as `#{foo}`, but it's available in case you\n (1) override the default escaping or (2) turn off auto-escaping (both explained below).\n- `#{partial \"foo.toffee\"}` and `#{snippet \"foo.toffee\"}`: unescaped, since you don't want to escape your own templates\n\nWhen any of the functions mentioned above are leftmost in a `#{}` token in toffee mode, their output is left untouched by the\nbuilt in escape function.\n\nThese functions are also available to you in coffee mode.\n\n```html\n\n Want to read some JSON, human? {# foo = [1,2,3, {bar: \"none\"}]\n foo_as_json_as_html = html json foo print foo_as_json_as_html #}\n
\n```\n\n_Note!_ if you pass a variable to the template called `json`, `raw`, or `html`, Toffee won't create these helper functions, which would override your vars.\nIn this case, you can access the escape functions through their official titles, `__toffee.raw`, etc.\n\nOverriding the default `escape`:\n\n- If you pass a variable to your template called `escape`, this will be used as the default escape. In toffee mode, everything inside `#{}` that isn't subject to an above-mentioned exception will go through your `escape` function.\n\nTurning off autoescaping entirely:\n\n- If you set `autoEscape: false` when creating the engine, the default will be raw across your project. (See more on that below under Express 3.x settings.)\n- Alternatively, you could pass the var `escape: (x) -> x` to turn off escaping for a given template.\n\n## Common Questions\n\n#### How does it compare to eco?\n\nEco is another CoffeeScript templating language and inspiration for Toffee.\nThe syntaxes are pretty different, so pick the one you prefer.\n\nOne big Toffee advantage: multiple lines of CoffeeScript just look like CoffeeScript. Compare:\n\nECO\n\n```\n<% if @projects.length: %>\n <% for project in @projects: %>\n <% if project.is_active: %>\n<%= project.name %> | <%= project.description %>
\n <% end %>\n <% end %>\n<% end %>\n```\n\nTOFFEE\n\n```html\n{# if projects.length for project in projects if project.is_active {:\n#{project.name} | #{project.description}
\n:} #}\n```\n\nWith Toffee's syntax, brackets enclose regions not directives, so your editor\nwill let you collapse and expand sections of code. And if you click on one of the brackets in most\neditors, it will highlight the matching bracket.\n\n#### Does it cache templates?\n\nIn Express 2.0, that's up to Express. When used in Express 3.0, Toffee asynchronously monitors known templates and recompiles them in the background when necessary. So you don't need to restart your production webserver whenever you edit a template.\n\n#### Does it find line numbers in errors?\n\nYes, Toffee does a very good job of that. There are 3 possible places you can hit an error in Toffee:\n\n- in the language itself, say a parse error\n- in the CoffeeScript, preventing it from compiling to JS\n- runtime, in the final JS\n\nStack traces are converted to lines in Toffee and show you where the problem is.\nBy default when Toffee hits an error it replies with some pretty-printed HTML showing you the problem.\nThis can be overridden, as explained below in the Express 3.0 section.\n\n### Does it support partials? (a.k.a includes)\n\nYes. In Express 2.0, Express itself is responsible for including other files, and they call this system \"partials.\" In Express 3.0 and in the browser,\nToffee defines the `partial` function, and it works as you'd expect.\n\n```html\n