I love this. I've felt for awhile that as an industry we should experiment with specialized forms of IO for specific tasks. I've protoyped some devices for rating tracks in iTunes (http://vimeo.com/24298670) and using a joystick to control move through code with a debugger. The keyboard, mouse, and touch screen are great for general purpose IO, but specific tasks can be preformed more efficiently with customized IO devices.
Vim clutch
51–60 of 227 posts
Re: Vim clutch
#52> Has anyone thought of this before? The 1992 paper "The Prevention of Mode Errors Through Sensory Feedback" [1] uses this exact mechanism. [1] http://research.microsoft.com/en-us/um/people/asellen/public... I've argued for years that vim is one of the few good examples of modal design since it allows for quick entry of the command grammar without modifiers and the command grammar is an excellent fit for the domain.…
VIM clutch does not seem to prevent mode errors, though. For that pedals need to have feedback. I.e., if one hits 'a' out of habit or accidentally, stepping consequently on the insert pedal would predictably enter 'i' character. That would be avoided if the pedal changed to pressed state depending on mode.
That said, for me as a pianist the idea of mode pedal looks pretty awesome. It just needs to be developed a bit further.
Re: Vim clutch
#53Re: Vim clutch
#54Interesting idea, I wonder about using it for the Ctrl key instead. I switched to vim some time ago and that's the bit I find most clumsy, especially given the placement on a Mac. I've remapped caps lock to Ctrl, which helps.
Re: Vim clutch
#55> Has anyone thought of this before? The 1992 paper "The Prevention of Mode Errors Through Sensory Feedback" [1] uses this exact mechanism. [1] http://research.microsoft.com/en-us/um/people/asellen/public... I've argued for years that vim is one of the few good examples of modal design since it allows for quick entry of the command grammar without modifiers and the command grammar is an excellent fit for the domain.…
VIM clutch does not seem to prevent mode errors, though. For that pedals need to have feedback. I.e., if one hits 'a' out of habit or accidentally, stepping consequently on the insert pedal would predictably enter 'i' character. That would be avoided if the pedal changed to pressed state depending on mode. That said, for me as a pianist the idea of mode pedal looks pretty awesome. It just needs to be developed a bit…
Just need to make sure pedal down is idempotent. Having the pedal send something like Shift+F2 and then `nmap i` `imap ` takes care of that. Escape is always idempotent so no issues there.
Re: Vim clutch
#56Very nice. But why put something like this on GitHub?!!
git/GitHub are not for code. They are for version control. Most common applications of git are in software (since things like MS Word et al. have their own implementation of revision history within the software package), but it's not limited to such.
Suppose he comes up with a better way to build the device. It would be good practice to have all versions available, something that isn't as easy to do with a website. Additionally, his target audience is people who use vim, which probably has a reasonably large overlap with git/GitHub users.
Re: Vim clutch
#57Interesting idea, I wonder about using it for the Ctrl key instead. I switched to vim some time ago and that's the bit I find most clumsy, especially given the placement on a Mac. I've remapped caps lock to Ctrl, which helps.
If you use KeyRemap4MacBook[1] you can map caps lock to Ctrl, but also map just tapping caps lock to escape. Be warned, the only problem with this set up is that it's so good that you'll have trouble using another one; I disabled it when I got a thinkpad and starting doing about 50% of my development on my x220 instead. After that I changed to using ctrl-[ or ctrl-c in place of escape for most everything.
Re: Vim clutch
#58Interesting idea, I wonder about using it for the Ctrl key instead. I switched to vim some time ago and that's the bit I find most clumsy, especially given the placement on a Mac. I've remapped caps lock to Ctrl, which helps.
OSX actually lets you remap all of the mod keys (Ctrl, Opt, Cmd, CapsLock) to each other system-wide in the keyboard prefs.
Re: Vim clutch
#59Interesting idea, I wonder about using it for the Ctrl key instead. I switched to vim some time ago and that's the bit I find most clumsy, especially given the placement on a Mac. I've remapped caps lock to Ctrl, which helps.
If you use KeyRemap4MacBook[1] you can map caps lock to Ctrl, but also map just tapping caps lock to escape. Be warned, the only problem with this set up is that it's so good that you'll have trouble using another one; I disabled it when I got a thinkpad and starting doing about 50% of my development on my x220 instead. After that I changed to using ctrl-[ or ctrl-c in place of escape for most everything. [1] http://…
Ah, ctrl-c for esc is a good idea.
Re: Vim clutch
#60Interesting idea, I wonder about using it for the Ctrl key instead. I switched to vim some time ago and that's the bit I find most clumsy, especially given the placement on a Mac. I've remapped caps lock to Ctrl, which helps.
Just out of interest, how often are you really using the ctrl key in a Vim session? My CapsLock is mapped to ESC, which I hit at the end of every edit (so several times per minute), but I don't think I use ctrl much at all.
OTOH I have heard Emacs users need Ctrl/Alt constantly while editing.