From: Charles Forsyth <charles.forsyth@gmail.com>
To: erik quanstrom <quanstro@quanstro.net>
Cc: 9fans@9fans.net, lucio@proxima.alt.za
Subject: Re: [9fans] Acme: the way the future actually was
Date: Fri, 14 Sep 2012 15:26:25 +0100 [thread overview]
Message-ID: <CAOw7k5gq00AEvDcNxUmL+WJhxG2tw-4kpHERn1N6MbYE_RZZQQ@mail.gmail.com> (raw)
In-Reply-To: <d76c4d501abff0ca6da3e12240c997cc@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
"Copy" is a little strong: inspired by, certainly, by way of help/help,
but there's an amazing difference in the structure of acme as "text editor
as file server"
with many independent clients accessing it through the file system.
Oberon had a more conventional module "plug-in" structure within a single
process.
Acme's user interface is also more strictly text-oriented, and streamlined
the mouse conventions.
On 14 September 2012 15:19, erik quanstrom <quanstro@quanstro.net> wrote:
> neither is knowledge of oberon ubiquitous among 9fans, who may
> not realize that acme itself is a copy.
>
[-- Attachment #2: Type: text/html, Size: 955 bytes --]
next prev parent reply other threads:[~2012-09-14 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 13:12 dexen deVries
2012-09-14 13:52 ` Charles Forsyth
2012-09-14 14:07 ` Lucio De Re
2012-09-14 14:10 ` Charles Forsyth
[not found] ` <CAOw7k5ggBBkJYOX_Qa-9Jh+h3D7wcYsmpjWyexFMba46LPvRrQ@mail.gmail.c>
2012-09-14 14:19 ` erik quanstrom
2012-09-14 14:25 ` Hugo Rivera
2012-09-14 14:26 ` Charles Forsyth [this message]
2012-09-14 16:48 ` Jack Johnson
2012-09-14 20:00 ` Anssi Porttikivi
2012-09-14 20:02 ` Anssi Porttikivi
2012-09-14 21:58 ` Nick LaForge
2012-09-14 23:15 ` hiro
2012-09-14 23:28 ` Matthew Veety
2012-09-17 18:24 ` Charles Forsyth
2012-09-17 18:26 ` Charles Forsyth
2012-09-18 6:03 ` Anssi Porttikivi
2012-10-25 14:28 ` Ethan Grammatikidis
2012-10-25 14:58 ` Dan Cross
2012-09-17 12:51 ` michaelian ennis
2012-09-18 13:51 ` michaelian ennis
2012-09-15 12:51 ` Aram Hăvărneanu
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=CAOw7k5gq00AEvDcNxUmL+WJhxG2tw-4kpHERn1N6MbYE_RZZQQ@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
--cc=quanstro@quanstro.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).