From: Dave Edmondson davided@sco.com
Subject: local and remote cpu resources and the acme model of interaction
Date: Mon, 24 Apr 1995 07:11:34 -0400 [thread overview]
Message-ID: <19950424111134.Z_XARWuBi5mS46aHj1Zpk_iuN8iSQSPmt8PEtsZOUnw@z> (raw)
: > 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.
next reply other threads:[~1995-04-24 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-24 11:11 Dave [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-26 20:09 serge
1995-04-25 15:45 Alberto
1995-04-25 14:49 Matthew K
1995-04-25 10:21 Gary
1995-04-25 9:37 Dave
1995-04-25 5:46 Matthew K
1995-04-24 15:07 rob
1995-04-24 10:24 Gary
1995-04-24 9:00 Dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950424111134.Z_XARWuBi5mS46aHj1Zpk_iuN8iSQSPmt8PEtsZOUnw@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).