From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 24 Apr 1995 07:11:34 -0400
From: Dave Edmondson davided@sco.com
Subject: local and remote cpu resources and the acme model of interaction
Topicbox-Message-UUID: 0d6a11b0-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19950424111134.Z_XARWuBi5mS46aHj1Zpk_iuN8iSQSPmt8PEtsZOUnw@z>

: > if i run it on the terminal, then i end up
: > compiling there.
: not if you type 'mk' in a window connnected to the cpu server.

this is the crux of my concern (at this point i should make it clear
that i've never actually used acme or help or plan9).  i guess that if
i can have typescript windows in acme, then i can have acme windows
where whatever i type is interpreted by a process on the cpu server
(start a typescript and then connect to the server).  then i can 'mk'
there and see the output, and presumably click in the appropriate way
to have acme find the files/lines/... as necessary.  what seems odd is
that i have to start a typescript window and then connect to the cpu
server.

i have read that plan9 doesn't attempt to move jobs around for me (the
process distribution is coarse), but this seems to be an area where
things don't fit together wonderfully.

i would also add that this exact problem exists if you use emacs on a
`terminal' and wish to compile on a `cpu server' - you can't use the
default lisp support for compiling programs and wandering through the
errors.