Re: Redefining command keys

[Matthew Campbell]

Well, it seems that touch-typable keys are always less intuitive than
the normal cursor movement keys.  And since some like vi and others
like Emacs, I'm not going to fllow either, at least not by default.
Here's another idea for the navigation keys.  I hope this will delay
the need for a runtime configuration file.

comma or left arrow: back 6 seconds
period or right arrow: forward 6 seconds
less-than or up arrow: back 1 minute
greater-than or down arrow: forward 1 minute
9 or page-up: back 10 minutes
0 or page-down: forward 10 minutes
left parenthesis or home: beginning of clip
right parenthesis or end: end of clip with automatic pause
left bracket: previous clip
right bracket: next clip
left brace: first clip
right brace: last clip

And some other keys that should probably be changed:

p: pause or resume playback (formerly control-p)
q: quit (formerly stop, control-s)
Q (capital): quiet mode toggle (formerly q)

I thought for a few seconds about keys to increase and decrease the
volume, but I concluded that that's what mixer programs like aumix are
for.  What do you think?

-- 
Matt Campbell
Web site:  http://www.crosswinds.net/~mattcamp/
ICQ #:  33005941