From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Samterm up down key patch
Date: Tue, 14 Nov 2006 23:57:26 -0500 [thread overview]
Message-ID: <7d3530220611142057t45ce0f89nc8a20dea219b92ac@mail.gmail.com> (raw)
In-Reply-To: <34D4933C-7C2E-4B31-A448-D630C8A699E1@orthanc.ca>
On 11/14/06, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> Where is the research data that backs the claim that navigating via
> the mouse is more efficient than navigating via the keyboard? I know
> my own experience says this is nonsense. My physical context switch
> time between the keyboard and mouse is at least 300 ms; my fingers
> move quite a bit faster than that on the keyboard. I know that when
> I'm in one of the two modes – kbd vs. mouse – I'm very quick in that
> context. But as soon as I have to switch between them: yikes! To
> bounce back and forth from typing source code to repositioning a few
> lines via the mouse to typing again is horribly inefficient. And
> while I've come to grow and love acme over the last few months now
> that I use it regularly at work, that back-and-forth makes me want to
> hurl (only the keyboard and mouse, mostly, but there are days ...)
Finally, another user that doesn't drink the mouse Kool-Aid; although
I use the mouse a moderate amount, using the mouse for cursor
positioning while editing code is indeed a terrible waste. I've looked
at the papers linked from the Plan 9 wiki about speed of mouse vs.
keyboard, and while it may be faster to go from point A to point B
using the mouse when A and B are far apart, the context switch and the
fact that often you're not moving that far kinda makes the point void.
John
--
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
next prev parent reply other threads:[~2006-11-15 4:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 1:02 Joey Makar
2006-11-14 10:49 ` Martin Neubauer
2006-11-14 13:04 ` erik quanstrom
2006-11-14 13:26 ` Martin Neubauer
2006-11-14 13:38 ` erik quanstrom
2006-11-14 18:04 ` David Leimbach
2006-11-14 13:25 ` ron minnich
2006-11-14 13:34 ` erik quanstrom
2006-11-14 13:44 ` ron minnich
2006-11-14 14:04 ` erik quanstrom
2006-11-14 14:16 ` Martin Neubauer
2006-11-14 14:42 ` maht
2006-11-14 16:48 ` Joel Salomon
2006-11-14 17:03 ` maht
2006-11-14 16:48 ` Joey Makar
2006-11-14 20:03 ` John Floren
2006-11-14 21:57 ` Russ Cox
2006-11-14 22:06 ` David Leimbach
2006-11-15 9:40 ` Matt
2007-01-30 9:55 ` Harri Haataja
2007-01-30 11:34 ` John Stalker
2006-11-14 18:10 ` David Leimbach
2006-11-14 18:21 ` Sape Mullender
2006-11-14 18:35 ` erik quanstrom
2006-11-14 18:52 ` Bruce Ellis
2006-11-14 19:14 ` Sape Mullender
2006-11-14 19:18 ` Paul Lalonde
2006-11-14 19:34 ` rog
2006-11-14 19:40 ` csant
2006-11-14 19:52 ` Bruce Ellis
2006-11-14 18:22 ` Bruce Ellis
2006-11-15 4:43 ` Lyndon Nerenberg
2006-11-15 4:57 ` John Floren [this message]
2006-11-15 5:13 ` Russ Cox
2006-11-15 5:32 ` John Floren
2006-11-15 9:27 ` Gorka guardiola
2006-11-15 14:09 ` David Arnold
2006-11-16 2:49 ` erik quanstrom
2006-11-16 13:46 ` plan9
2006-11-16 13:55 ` Abhey Shah
2006-11-17 16:44 ` erik quanstrom
2006-11-20 5:48 ` Noah Evans
2007-01-30 11:28 ` Harri Haataja
2007-01-30 11:35 ` Russ Cox
2007-01-30 11:45 ` Gabriel Diaz
2006-11-15 5:28 ` Lyndon Nerenberg
2006-11-15 16:26 ` David Leimbach
2006-11-14 14:08 ` Martin Neubauer
2006-11-14 14:20 ` Wes Kussmaul
2006-11-14 15:07 ` Wes Kussmaul
2006-11-14 18:03 ` David Leimbach
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=7d3530220611142057t45ce0f89nc8a20dea219b92ac@mail.gmail.com \
--to=slawmaster@gmail.com \
--cc=9fans@cse.psu.edu \
/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).