🚀 go-pugleaf

In article <1992Apr7.000402.69@unixg.ubc.ca> jeffrey@squid.tram.com writes:
>If you write a program and run it in place of the default Windowproc
>you lose *all* of the escape code handling!

Of course -- your application may have other uses for the data stream.

>This means that if I want to do any of the fancy curses-style
>processing, I have to either one of two things.  First off, I can
>re-implement the Windowproc to handle all the escape sequences I want.

This has been done, in the new-S package (licensed by AT&T).  There
were a few bugs which I have fixed in our version; if you want the
"diff" listing showing the bug fixes, let me know.

>The second option ... is to use the ROM image of Windowproc as a sort
>of library.

What I would also like to know is how one can do this decently.  Even
if you build in your own terminal emulator, you still lose the scroll
bars and mouse editing.  I'd like to be able to construct essentially
the following in the terminal

	HOST_CHANNEL <----> FILTER <----> DEFAULT_WINDOWPROC

where the "FILTER" is a downloaded application that inspects data
traffic and either passes it along or else consumes it with some
special action.  For example, in the case of the S terminal part,
it would look for a "begin graphics mode" code and once seen would
intercept all subsequent data, making plots etc. until an "end
graphics mode" code were seen.  (While not in graphics mode, one
would have full use of the Windowproc text support features.)

This is basically a job for "STREAMS", which the 630 doesn't appear
to have, but perhaps there is an adequate substitute available.  If
so, I hope somebody tells us about it!