From: mike@majestix.cs.uoregon.edu mike@majestix.cs.uoregon.edu
Subject: oops
Date: Mon, 5 Jul 1993 13:39:29 -0400 [thread overview]
Message-ID: <19930705173929.MO9OePg7ifI_wTjRwMJJLsuyfMFxnSh4qcD49vxr0bs@z> (raw)
Unthinkingly, I wrote:
>I think the only place where the "plan 9 model" is dramatically
>different is in window system software.
I should clarify this: In Unix, most programs take standard input
and produce standard output. The same is true in Plan 9. So when
I said the plan 9 model is mostly the same, I was thinking of how
you run programs, not how you write them. The incompatibilities
are a bit more dramatic from a programmer's point of view.
reply other threads:[~1993-07-05 17:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19930705173929.MO9OePg7ifI_wTjRwMJJLsuyfMFxnSh4qcD49vxr0bs@z \
--to=mike@majestix.cs.uoregon.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).