From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 25 Apr 1995 11:45:04 -0400
From: Alberto Nava beto@plan9.cs.su.oz.au
Subject: local and remote cpu resources and the acme model of interaction
Topicbox-Message-UUID: 0d785fe0-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19950425154504.ZJsvYKGxEt5W1iXHdR3qloS8iuawGtqgz8sAXGSNyKA@z>

In <199504241111.MAA08305@netlab.london.sco.com>
	Dave Edmondson <davided@sco.com> wrote:

> : > 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.
> 

You do not need to start a window connected to the cpu
server in order to run something there. Just type 'cpu -c mk', and
It will do the job. So 'mk' is local and 'cpu -c mk' is remote.