From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Lyndon Nerenberg In-Reply-To: <20160519215144.GG22691@wopr> Date: Thu, 19 May 2016 17:37:16 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <461FFF1E-B3DA-43E1-BC4C-1672E4C628A6@orthanc.ca> References: <20160519215144.GG22691@wopr> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] problem with acme on 9front Topicbox-Message-UUID: 90a7a8ec-ead9-11e9-9d60-3106f5b1d025 > On May 19, 2016, at 2:51 PM, Kurt H Maier wrote: >=20 > Acme is firmly with X Windows in the "huge programs that don't = actually > *do* anything for you" category. To my view, acme is more of an IDE than an editor. the << = B3-on-file:linenum >> in the diagnostics window from a compile is the = greatest productivity gain I have ever experienced. I do like how I can = use the "window control " extensions acme provides to write helper = scripts for that environment. But again, these are almost always = IDE-oriented things that I only use during compile/debug/compile/debug. I have never been able to get my head around sam's user interface, at = least to the point where I would be using it as it was intended. I love = it in '-r' mode on UNIX when I need to edit something on the other end = of a horribly inconsistent VPN tunnel. But really, for most plain text = editing needs (troff docs, system config files, etc), I'm happy to plod = along with ed(1).