9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: Re: [9fans] release -1 of smacme
Date: Fri,  7 Jul 2006 08:31:26 -0700	[thread overview]
Message-ID: <3e1162e60607070831q35be209asca45b071deebc1cf@mail.gmail.com> (raw)
In-Reply-To: <7d3530220607070753l69e4ec8bw86366713c27330e5@mail.gmail.com>

> > The same argument holds for why pointing and clicking the mouse 30
> > lines down is faster than hitting down 30 times so I don't see that as
> > a violation of the spirit of what Acme is supposed to be very good at.
> >
> > The original author may disagree with me.
> >
> > The snarf comment was just an attempt to get "smacked" ;-).  The fact
> > that I have mouse chording alone means that this feature would have
> > been duplicate and probably not as good as what's already there.
> I wouldn't mind a shortcut to paste. When snarfing, the hand is
> already on the mouse anyway, but if I want to paste multiple times
> over time, I'd like to do it with hands on the keyboard.

This is one of those times where a personal preference may make you
really want to make this change.  Ron's code is out there :-).

Honestly, I find chording fits in better with my workflow.  In fact,
I've often wondered why the chording keyboard never made it.  Douglas
Englebart seemed to like it.

Seems like the sort of thing geeks would drool over if they could master it :-)

I mean, my mother who was a typist used foot pedals for dictation
machines, why'd she have all the cool shortcuts?

I should talk to my EE buddies and see if we can make such a thing
someday, unless people know of a good chording keyboard that already
exists.

>
> > Dave
> >
>
>
> --
> TANSTAAFL! (There Ain't No Such Thing As A Free Lunch!)
>


  reply	other threads:[~2006-07-07 15:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 22:18 Ronald G Minnich
2006-07-07  1:18 ` Federico Benavento
2006-07-07  5:00 ` David Leimbach
2006-07-07  5:03   ` Rob Pike
2006-07-07  5:07     ` David Leimbach
2006-07-07 14:07       ` Ronald G Minnich
2006-07-07 14:34         ` David Leimbach
2006-07-07 14:51           ` Ronald G Minnich
2006-07-07 14:53           ` John Floren
2006-07-07 15:31             ` David Leimbach [this message]
2006-07-07 16:07               ` Jack Johnson
2006-07-07 16:09                 ` C H Forsyth
2006-07-07 16:20                 ` David Leimbach
2006-07-07 16:00             ` C H Forsyth
2006-07-07 16:27               ` uriel
2006-07-07 16:45                 ` jmk
2006-07-07 20:08                   ` Brantley Coile
2006-07-07 20:21                     ` David Leimbach
2006-07-08  3:00                   ` Ronald G Minnich
2006-07-08  2:59                 ` Ronald G Minnich
2006-07-07 14:05   ` Ronald G Minnich
2006-07-07  6:16 ` Christoph Lohmann
2006-07-07 14:09   ` Ronald G Minnich
2006-07-07 14:17     ` Christoph Lohmann
2006-07-07 14:27       ` Ronald G Minnich
2006-07-07 19:53     ` uriel
2006-07-07 20:23       ` jmk
2006-07-07 20:35         ` David Leimbach
2006-07-08  2:38         ` uriel
2006-07-08  3:45           ` jmk
2006-07-08  3:39             ` quanstro
2006-07-08  4:26               ` jmk
2006-07-08 12:30                 ` quanstro

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=3e1162e60607070831q35be209asca45b071deebc1cf@mail.gmail.com \
    --to=leimy2k@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).