From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] problem with acme on 9front
Date: Fri, 20 May 2016 02:23:11 +0100 [thread overview]
Message-ID: <1463707391.4126990.613229361.7308302E@webmail.messagingengine.com> (raw)
In-Reply-To: <461FFF1E-B3DA-43E1-BC4C-1672E4C628A6@orthanc.ca>
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.
next prev parent reply other threads:[~2016-05-20 1:23 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 [this message]
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
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=1463707391.4126990.613229361.7308302E@webmail.messagingengine.com \
--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).