From: serge@euler.Berkeley.EDU serge@euler.Berkeley.EDU
Subject: local and remote cpu resources and the acme model of interaction
Date: Wed, 26 Apr 1995 16:09:30 -0400 [thread overview]
Message-ID: <19950426200930.Ix1fKLgNdcS2XeLn_cPiIxb2ZxTZ6-7EJhY2ETxwn0M@z> (raw)
>on a seperate note, thinking about how graphics might work in acme -
>what /dev/mouse, /dev/bitblt, ... do acme's clients see ?
Probably /dev/ocr will be sufficient. :-)
>poisoned ones ?
Eh?
next reply other threads:[~1995-04-26 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-26 20:09 serge [this message]
-- strict thread matches above, loose matches on Subject: below --
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 11:11 Dave
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=19950426200930.Ix1fKLgNdcS2XeLn_cPiIxb2ZxTZ6-7EJhY2ETxwn0M@z \
--to=serge@euler.berkeley.edu \
/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).