From mboxrd@z Thu Jan 1 00:00:00 1970 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable From: stanley lieber Date: Thu, 19 May 2016 16:53:01 -0400 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <240B21E7-6FB4-45E3-9E59-7B3635D6C4C2@9front.org> Subject: Re: [9fans] problem with acme on 9front Topicbox-Message-UUID: 906eed40-ead9-11e9-9d60-3106f5b1d025 >> 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 lo= t of plumber rules (or arrange to maintain multiple sets of rules for acme = and not-acme)=2E Because of the way acme manages windows, programs often ne= ed to keep track of (and handle) whether or not they are running inside acm= e=2E Finally, acme does not support some common features provided by rio (l= ike hold mode), which means even some text-based programs (like upas/marsha= l) aren't fully functional=2E Everything acme touches requires special hand= -holding=2E Conceptually, it is the opposite of the tools approach to softw= are=2E As I said, this can be convenient on a UNIX system that otherwise lacks th= e features provided by rio, but on Plan 9, where most of this stuff is othe= rwise already available, it requires a great deal of commitment to the acme= grab-it-all philosophy=2E Sometimes, you don't want to carry the kitchen s= ink on your back=2E sl