From: dbecker@jupiter.Legato.COM (Doug Becker)
To: plan9-fans@cse.psu.edu, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: acme for X?
Date: Tue, 6 Dec 1994 18:03:56 -0500 [thread overview]
Message-ID: <9412062303.AA05245@jupiter.Legato.COM> (raw)
In-Reply-To: <94Dec6.171159est.295241@psuvax1.cse.psu.edu> from "philw@plan9.research.att.com" at Dec 6, 94 05:02:24 pm
Not that Phil's response is in any way lacking (I had no idea of the
port of ALEF to UNIX), but I asked Rob the same question a couple of
weeks ago, and his response was that Acme is "pretty deeply wedded"
to concepts in Plan 9 that have no analog in UNIX. (This seems fairly
obvious from the various papers.)
I too would love to see some sort of Acme under UNIX (or even Plan 9. :-)
Heck, just the general availability of Acme's ALEF source would be enough
to appease me for a few weeks... :-)
next parent reply other threads:[~1994-12-06 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94Dec6.171159est.295241@psuvax1.cse.psu.edu>
1994-12-06 23:03 ` Doug Becker [this message]
1994-12-07 3:34 ` Scott Schwartz
1994-12-07 11:11 pete
-- strict thread matches above, loose matches on Subject: below --
1994-12-06 21:22 Bill Trost
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=9412062303.AA05245@jupiter.Legato.COM \
--to=dbecker@jupiter.legato.com \
--cc=plan9-fans@cse.psu.edu \
--cc=sam-fans@hawkwind.utcs.toronto.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).