From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 16:44:59 +0100 [thread overview]
Message-ID: <20090715164459.a40763e6.eekee57@fastmail.fm> (raw)
In-Reply-To: <3BBB12CF4EFF4040B38542759379E3CD0278ED@XMAIL.asuch.cas.cz>
On Wed, 15 Jul 2009 17:32:09 +0200
<cej@gli.cas.cz> wrote:
>
>
> > I also take issue with the statement "Acme is a text editor," that never sounds right, no more than describing Emacs as
> > a text editor. It's natural to use Acme as a text editor and it provides many more text-editing facilities than Rio
> > does, but it is also natural to use it as a file manager, shell window provider, email client, etc, etc.
> > It provides more than Rio and it does it all with tiling windows and without menus, but that's just style.
>
> I always thought of using Acme as 'The' UI for Plan 9, much in the Oberon way. I'm not a techie, but I use Plan 9 since 2000, or so, as my main OS. I would *way* love having graphics in Acme, asi it IS a great UI, IMHO.
As-is it's actually not a great UI for me, but perhaps with some small changes it could be. I'm still thinking those changes over.
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-07-15 15:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 1:58 Jason Catena
2009-07-15 4:36 ` Rob Pike
2009-07-15 5:02 ` David Leimbach
2009-07-15 13:11 ` Charles Forsyth
2009-07-16 9:58 ` cej
2009-07-16 10:41 ` mattmobile
2009-07-16 12:11 ` michael block
2009-07-16 12:29 ` cej
2009-07-15 9:25 ` Paul Donnelly
2009-07-15 12:22 ` Ethan Grammatikidis
2009-07-15 15:32 ` cej
2009-07-15 15:44 ` Ethan Grammatikidis [this message]
2009-07-15 17:00 ` John Floren
2009-07-15 18:24 ` Francisco J Ballesteros
2009-07-15 18:26 ` Steve Simon
2009-07-15 18:59 ` David Leimbach
2009-07-15 19:07 ` John Floren
2009-07-15 19:27 ` David Leimbach
2009-07-15 20:58 ` Chad Brown
2009-07-15 21:07 ` John Floren
2009-07-15 19:54 ` Jason Catena
2009-07-15 19:59 ` erik quanstrom
2009-07-15 20:05 ` andrey mirtchovski
2009-07-15 20:14 ` Devon H. O'Dell
2009-07-15 20:29 ` Jason Catena
2009-07-15 20:42 ` Noah Evans
2009-07-15 20:51 ` David Leimbach
2009-07-15 21:27 ` Ethan Grammatikidis
2009-07-15 23:31 ` Jason Catena
2009-07-15 21:07 ` Ethan Grammatikidis
2009-07-15 21:12 ` erik quanstrom
2009-07-15 21:32 ` Ethan Grammatikidis
2009-07-15 20:41 ` Lyndon Nerenberg
2009-07-15 21:00 ` Federico G. Benavento
2009-07-15 21:14 ` David Leimbach
2009-07-16 8:51 ` Paul Donnelly
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=20090715164459.a40763e6.eekee57@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=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).