From: stanley lieber <sl@9front.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem with acme on 9front
Date: Thu, 19 May 2016 16:53:01 -0400 [thread overview]
Message-ID: <240B21E7-6FB4-45E3-9E59-7B3635D6C4C2@9front.org> (raw)
In-Reply-To: <CAOw7k5gbX7OUM-m5T4E1kx0GbNNZgL6BH0TvYhED2NyTZ=CQ6w@mail.gmail.com>
>> at the cost of stepping all over the rest of the (Plan 9) system
>
>
>?
To get the best use out of acme you need to arrange for it to capture a lot of plumber rules (or arrange to maintain multiple sets of rules for acme and not-acme). Because of the way acme manages windows, programs often need to keep track of (and handle) whether or not they are running inside acme. Finally, acme does not support some common features provided by rio (like hold mode), which means even some text-based programs (like upas/marshal) aren't fully functional. Everything acme touches requires special hand-holding. Conceptually, it is the opposite of the tools approach to software.
As I said, this can be convenient on a UNIX system that otherwise lacks the features provided by rio, but on Plan 9, where most of this stuff is otherwise already available, it requires a great deal of commitment to the acme grab-it-all philosophy. Sometimes, you don't want to carry the kitchen sink on your back.
sl
next prev parent reply other threads:[~2016-05-19 20:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 18:30 christophe DAMAS
2016-05-19 18:40 ` Siarhei Zirukin
2016-05-19 19:42 ` Charles Forsyth
2016-05-19 21:51 ` Kurt H Maier
2016-05-20 0:37 ` Lyndon Nerenberg
2016-05-20 1:23 ` Ethan Grammatikidis
2016-05-20 1:32 ` Lyndon Nerenberg
2016-05-20 2:02 ` Ethan Grammatikidis
2016-05-20 2:07 ` Lyndon Nerenberg
2016-05-20 11:58 ` hiro
2016-05-20 12:07 ` Mark van Atten
2016-05-20 15:49 ` Wes Kussmaul
2016-05-20 12:12 ` Brantley Coile
2016-05-20 20:01 ` Steve Simon
2016-05-21 21:52 ` Mark Lee Smith
2016-05-21 23:18 ` erik quanstrom
2016-05-22 7:36 ` Siarhei Zirukin
2016-05-22 17:28 ` Mark Lee Smith
2016-05-21 17:36 ` erik quanstrom
2016-05-21 18:16 ` Kurt H Maier
2016-05-21 18:28 ` Rob Pike
2016-05-21 19:21 ` Kurt H Maier
2016-05-21 23:14 ` Lyndon Nerenberg
2016-05-19 18:41 ` cinap_lenrek
2016-05-19 19:20 ` Mark Lee Smith
2016-05-19 19:36 ` cinap_lenrek
2016-05-19 20:26 ` Mark Lee Smith
2016-05-19 20:37 ` Lee Fallat
2016-05-19 20:40 ` Aram Hăvărneanu
2016-05-19 20:11 ` stanley lieber
2016-05-19 20:15 ` Charles Forsyth
2016-05-19 20:53 ` stanley lieber [this message]
2016-05-19 21:13 ` Mark van Atten
2016-05-19 21:18 ` Lee Fallat
2016-05-21 19:08 ` Mark van Atten
2016-05-21 19:23 trebol55555
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=240B21E7-6FB4-45E3-9E59-7B3635D6C4C2@9front.org \
--to=sl@9front.org \
--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).