From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1463707391.4126990.613229361.7308302E@webmail.messagingengine.com> From: Ethan Grammatikidis To: 9fans@9fans.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Date: Fri, 20 May 2016 02:23:11 +0100 In-Reply-To: <461FFF1E-B3DA-43E1-BC4C-1672E4C628A6@orthanc.ca> References: <20160519215144.GG22691@wopr> <461FFF1E-B3DA-43E1-BC4C-1672E4C628A6@orthanc.ca> Subject: Re: [9fans] problem with acme on 9front Topicbox-Message-UUID: 90afb38e-ead9-11e9-9d60-3106f5b1d025 On Fri, May 20, 2016, at 01:37 AM, Lyndon Nerenberg wrote: > 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. It's the plumber which does the heavy lifting there, and it will provide the same in conjunction with rio & sam. Selecting 'plumb' from rio's menu may seem clunkier, but after the first time it's just a b2click without reselecting, unless of course you do anything else with the b2 menu in between. Having said that, I prefer Acme anyway. Its window tiling often becomes a nuisance, but it's a minor one. Sam's dual clipboard is a far bigger nuisance in my many-window environment. Acme's small, mouse-focus tag bars are sometimes irritating, but now the tag bars expand you can keep multiple commands handy much more simply than in rio or sam. Acme's changing the length of the tag text can be quite awful when it jumps between single and multiple lines when editing, but again, it doesn't interfere like Sam's dual clipboard. Also, I find Sam's menus a good deal worse than rio's; I find myself needing to switch menu elements far more often. 9front's addition of chording to Sam helps, but it's buggy and (due to the dual clipboards) I haven't used Sam enough to know if it's enough. -- Wir mussen wissen, wir werden wissen.