🚀 go-pugleaf

This is a question for you KA9Q Borland C gurus.

In spite of my total ignorance of C I've been porting the JNOS command 
history into Demon's KA9Q with the hope that it would find it's way into 
Textwin. (I can't compile TW since I only have BC3.)
So far, so good, and I've extended the command history to cover all TTY 
"cooked" sessions and added the ability to edit recalled commands. I got 
persuaded to do a few other things for somebody (extended help, command 
line ftp scripting, etc) and that's gone OK as well.

Now to the point of all this. I dislike KA9Q's cryptic mono interface 
and since I've had to run my "Tinynet" KA9Q a lot I've flashed it up 
with controllable colour and, getting cocky here :), a couple of 
JNOS-style status lines. It works OK, but I'm puzzled. In spite of 
defining a window which the screen output initially honours (it starts 
output at the correct line), when it scrolls it scrolls the whole bloody 
screen and not just the defined window. Why ? JNOS, WNOS, etc have 
status lines, but the screen scrolls within the defined window and they 
don't *appear* to do their output in a different way, but obviously they 
do. It's not a big thing, but it's starting to bug me :)  Any ideas ?

Ian.
-- 

  |  Ian Smith            | "The Moving Finger writes;
  |  ian@isis.demon.co.uk |  and, having writ, Moves on."