JdBP>   I cannot see why the implementors of AVIO 
 JdBP> wouldn't use the same code
 JdBP>   for writing to an AVIO cell array as they would 
 JdBP> for writing to an LVB,
 JdBP>   so it's a fair guess that the escape sequences 
 JdBP> would work, what few
 JdBP>   there are of them.
 
   I think that at the time, AVIO was meant to be something a little more
(not a lot, but a little) more than just a VIO space that shows up under
PM. In particular, they allow relocatable coordinate origins (VioSetOrg() )
which aren't supported for VIO. This makes the exact meaning of coordinates
in the space uncertain (e.g. 0,0 in the space could very well be invisible)
so supporting cursor positioning in the ANSI support might not behave as
intended - every where else that cursor coordinates show up,the coordinate
convention is easily taken care of by the calling code, but to change them
in an ANSI stream would require parsing the stream.
   Of course, they could have included support for cursor positioning with
the requirment that the origin be (0,0). Actually, now that I think of it,
it's conceivable that they did - all I remember for sure is that when the
origin isn't (0,0) (never has been in my code) cursor positioning codes are
just swallowed without effect.

--- Maximus/2 2.02p1