Changes

local visualizer = buffers.newvisualizer('foo')

<code>newvisualizer</code> to). Each of the function headers in the hooklist below use this.

== Defining hooks ==For example, after registering the 'foo' prettyprinter as above, the<tt>flush_line</tt> hook should be defined as:  function visualizer.flush_line(str,nested) Each pretty printer should can define a number of hook functions. Each of

are free to handle the input in any way. Each See below for when and how ahook is called. Defining a hook is optional, if it isnot defined, a default version will be called instead. == Hooks ==This section lists all hooks available to a pretty printer. Firstwe'll show how and when the hooks are called.

When pretty printinga file or buffer (named or anonymous using<code>\starttyping</code>), the following hooks are called:

Each hook should be defined as function named as follows:When prettyprint a single phrase (using <ttcode>buffers.visualizers.''printer_name''.''function_name''\type</ttcode>), the followinghooks are called:

For example, the # Call <tt>begin_of_inline</tt># Call <tt>flush_line</tt> function for the # Call <tt>fooend_of_inline</tt>pretty printer, above should be defined as:

function buffers.visualizers.foo.flush_line(strNote that in this case,nested) == Hooks ==the <tt>line</tt> hook is not called!

<tt>[[source:buff-ini.lua</tt> |buff-ini.lua]] (which is called by <tt>[[source:buff-ini.mkiv</tt> |buff-ini.mkiv]] and<tt>[[source:buff-ver.mkiv|buff-ver.mkiv</tt> ]] from the TeX side), in the ConTeXt distribution.