PF>>> You don't have to update the screen (or the physical cursor) between
 PF>>> codes.   Only update when you have no more data.

 MK>> VioGetBuf/VioShowBuf
 
 LH>Did you read past the first word of that message?

Yep.  VioGetBuf gives you the location of the Logical Video Buffer.
VioShowBuf updates the screen from that buffer.  You can do it when you
have no more data to display, as Peter said and you asked "how do I do
that?"

 LH> I was well aware that there's a few API calls to dump out multiple
 LH> characters

RTFM -- that's not what the above two calls do.  They do allow you to
manipulate the LVB and update the screen when ready.

 LH> have them handle all cursor movements and control codes

Of course you'd do that -- see Bob Stout's C_ECHO Snippets for example
code (it's in C, but I assume you can translate.  If not, you just need
a relatively simple state machine).

 LH> So unless VioShowBuf takes care of control codes

Of course it doesn't -- neither does poking directly into video memory
(as in DOS), which is what you were comparing to (remember? :-).  But it
will allow you to "write a byte at a time" and remain
"efficient,"
though I personally find that VioWrt* (excluding VioWrtTTY) are quite
adequate.

--- XHEd-OS/2 1.22