TODO
====

-	add documentation about scrolling & output behaviour?
-	add #defines for flow control

Any ideas?
From dhog@plan9.cs.su.oz.au Tue Mar  8 00:13:49 1994
Received: by staff.cs.su.oz.au with postie; Tue, 08 Mar 1994 00:13:49 +1100
Received: by staff.cs.su.oz.au with MHSnet; Tue, 08 Mar 1994 00:13:47 +1000
Received: by basser.cs.su.oz.au with MHSnet; Tue, 08 Mar 1994 00:13:45 +1000
Received: from plan9.cs.su.oz.au by MHSnet id 3hSnNX46p+SnNK; Tue, 08 Mar 1994 00:13:42 +1000
Received: from lore.plan9.cs.su.oz.au (insecurely) by joyce.cs.su.OZ.AU;
	Tue, 08 Mar 1994 00:12:35 +1000
Date: Tue, 8 Mar 1994 00:09:51 EST
From: David Hogan <dhog@plan9.cs.su.oz.au>
To: matty@cs.su.oz.au (James Matthew Farrow)
Subject: Re: 9term and 9wm...
X-Frobozz-Id: <19940308001351.0.in.frobozz@staff>

> What sort of support for 9wm do you want to see in 9term?

1.  9term should desist from adding its own extra border if 9wm is
    running (or if told not to by resource/option).  It should look
    for a resource called 9WM_RUNNING, and if it exists _and_ contains
    a valid window id, then 9wm is running.  (note that I haven't
    actually added this feature to 9wm yet...)

2.  9term should provide a resource on its top level window whose
    contents represent whether or not it is in hold mode.  When the
    mode changes, the resource changes, and 9wm can find this out by
    soliciting PropertyNotify events.

When all the appropriate changes have been made to both 9term and 9wm,
we should check that it looks the same as 8½ (:-)
