From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 1 Jul 2009 22:30:48 +0100 From: Ethan Grammatikidis To: 9fans@9fans.net Message-Id: <20090701223048.9bb1d0ef.eekee57@fastmail.fm> In-Reply-To: <3e1162e60907011358w7662ff53je2304e7266c2fa8e@mail.gmail.com> References: <20090701192454.GA31691@jg.domain_not_set.invalid> <3e1162e60907011358w7662ff53je2304e7266c2fa8e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Guide to using Acme effectively? Topicbox-Message-UUID: 12826226-ead5-11e9-9d60-3106f5b1d025 On Wed, 1 Jul 2009 13:58:19 -0700 David Leimbach wrote: > On Wed, Jul 1, 2009 at 12:49 PM, Russ Cox wrote: > > > Arguing about mouse vs keyboard misses the point. > > I'm very happy with acme's use of the mouse, but > > acme's power comes from the rest of its design. > > > > Russ > > > > > Even in Emacs, I use the mouse because pointing the insertion point or > cursor or whatever to where I need to type next is *much* faster than many > repetitions of a keypress a lot of the time. Me too, I require vi with X or Xterm mouse support. :) The mouse is not faster than vi's beginning/end of paragraph operations though, nor being able to set or goto "marks" with just 2 keypresses. Then there's "find matching bracket" which can be invaluable depending on language, goto beginning/end of sentence which is great when you've just typed something really stupid in your human-language narrative. There's the vi way of facilitating deletion or changing text in a region defined by any cursor motion, that can be hugely faster than select+delete with the mouse. I'm not saying vi is brilliant. Apart from the features listed above it has many which require more effort to recall than they're worth. It's idea of requiring the cursor to be on a character is obstructive, as are some of the features designed around that. -- Ethan Grammatikidis Those who are slower at parsing information must necessarily be faster at problem-solving.