Write

int Write(int * argc, void * args[]) {
(*argc)++;
while(args[*argc] && ((char*) args[*argc])[0] !=';') {
write(flush_fd,args[*argc],strlen(args[*argc]));
*argc +=1;
}
return(SUCCESS);
}

 On the command line:

Write a few tokens each stored as a string;

It is all tokens by now, my command line has been tokenized. he command is limited, at the moment, as I have no way to register the '\n' which plays a big role in marking y order.. My system has no quotes, and I am in no hurry to put quotes in the picture. Technically the tokenizer can see the quote, and it generates a scalar string, I have not used it.

But write was given to flush, it owns that name. Flush is the first level for unstructured data in this system.

I can put the text up with

Flush; FlushText;

A compound. It is awkward, and we will soon use signals and the text is moved to screen ASAP. The default callback for flush is to put it to console, a round trip, but it does test the  system. It is meant to connect to xchars and manage counting inY and finding X markers.

Flush handles redraw because in default this is all you get, a scrolling text window with no pretty overlays.  But, like I said before, the concept is reusable. One can make a different restructuring out of the fifo, maybe feed the sql machines, or the game rendering machine.,  This same ffush implementation can keep as tack of fifo pairs and manage scroll for multiple rectangles.  In general there is a lot of possibilities in feeding rectangles.