v0.5 3 months ago

* Clearly separate macro definitions from macro calls. Previously there were
  some edge cases where the parser would get confused if {=macroname}
  represents the start of a macro definition or calls the macro. Now, macros
  are defined with the {=!macroname}{/=!macroname} construct, and called as
* Correct the manpage with regards to macro definitions from includes - they
  *do not* carry over to the including source.