Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver (info-mac)
Newsgroups: fa.info-mac
Subject: Re: Instant Pascal
Message-ID: <1331@uw-beaver>
Date: Thu, 26-Jul-84 13:24:30 EDT
Article-I.D.: uw-beaver>.1331
Posted: Thu Jul 26 13:24:30 1984
Date-Received: Fri, 27-Jul-84 07:29:30 EDT
Sender: daemon@uw-beave
Organization: U of Washington Computer Science
Lines: 21

From: Rick McGeer (on an aaa-60-s) <mcgeer%ucbchip@Berkeley>
	Well, since you asked....
	
	The ideal programming environment would permit me the full power of
Gosling's emacs, with load intelligently shared between my Mac and the
mainframe.  As I write this, I have two shells and a Lisp running within my
emacs; as well I'm reading and responding to my mail, editing a major
program, and touching up that program's documentation.

	This obviously requires more than a simple protocol.  However, for
this to work, the protocol would have to permit the Mac to have more than
one window multiplexed over a single data line, since ideally each interactive
process would would deal with a separate window.  Further, block data would
have to go down the same line, since I presume that it's preferable to most
of us to do editing locally.  Finally, it would be nice if processes on the
other end could open up more than one window on the Mac, so that error
messages (say) weren't intermixed with output...

	Frankly, the dividing line between the layers of application are a
little fuzzy to me at this point.