Live data from Hacker News

Build muscle memory with your favorite editor

shortcutfoo.com

111–120 of 122 posts

Re: Build muscle memory with your favorite editor

#111

This really didn't work for me. I found needing to parse the command ("Move backward a word") broke the memory that I have built up over 15 years of using Emacs. Instead of naturally moving backwards with a flick of the fingers, I had to concentrate on where each finger was and on the key I was pressing. I think the goal of this is great, but as it stands, I'm not convinced it is going to help. Given it aborted my na…

Further, I don't want to need muscle memory for editing! I would take the hard stand that any repetitive keystroke combinations inherently implies inefficiency - ie, an ideal editor should provide enough shortcuts to give your keystroke stream a fairly high entropy content. Maybe we're not there yet but I don't want to develop habits which would stand in the way of such an ideal.

But that's what the muscle memory is for. If you only ever used the arrow keys to move around and backspace to delete one character at a time, you won't need any special tool for memorizing which key to use!

The whole reason this tool exists is because the best text editors (Emacs ;)) do have a ton of different commands. So now you have to learn that when you wand to delete a word in front you use M-d.

The "muscle memory" is just associating each of the many discrete keystrokes with an action. So instead of thinking "hmm, I need to delete this word, I'll press M-d" your hands just go to M-d as soon as you realize the word needs to be deleted.

This is exactly the sort of memory you need to deal with a high-entropy command stream quickly. The ideal would be to use a ton of different commands without thinking about them at all.

Now, I don't think this site is ideal for this sort of learning, but it's a step in the right direction.

Re: Build muscle memory with your favorite editor

#112

This really didn't work for me. I found needing to parse the command ("Move backward a word") broke the memory that I have built up over 15 years of using Emacs. Instead of naturally moving backwards with a flick of the fingers, I had to concentrate on where each finger was and on the key I was pressing. I think the goal of this is great, but as it stands, I'm not convinced it is going to help. Given it aborted my na…

>This really didn't work for me. I found needing to parse the command ("Move backward a word") broke the memory that I have built up over 15 years of using Emacs. Instead of naturally moving backwards with a flick of the fingers, I had to concentrate on where each finger was and on the key I was pressing. ...

>Now, take @gruseom's idea of a visual "goal" that you are chasing, and I think this could be intensely valuable.

I made exactly your suggestion to the author a while back, since this site was posted on HN about a month ago. A few days after that, I went to a TrueCar Ruby meetup where the author presented his shortcutfoo app, and when he asked for input, I made exactly your suggestion:

Since, I reasoned, you never go from "verbal description of alteration" to "keyboard input" in actual practice, I said that it would make more sense to give some visual representation of what the desired change looks like, since that is a lot closer to how people use these shortcuts (although not an exact match, of course). Someone else then followed up by suggesting that it display "before and after" pictures (what the text/cursor look like before and after the modification), which would be pretty easy to implement.

I don't know why he didn't take that suggestion, but it's unfortunate that he hasn't.

Earlier post: http://news.ycombinator.com/item?id=4007096

Re: Build muscle memory with your favorite editor

#114

Wow. Nothing like waking up on Monday morning to find your app at the top of Hacker News. Thanks to whoever posted this :) This is awesome feedback. It looks like the most requested feature right now is moving from reading words to a more visual representation of what's happening. This is definitely something I've thought about - but didn't want to attempt until I received exactly this type of response. Thanks! I'll…

Can you send an email when/if you implement that? I think there are lots of people that would be more willing to buy it if you have that.

Re: Build muscle memory with your favorite editor

#116
post #21
post #10

I have to enable way too much stuff in NoScript to proceed when I actually click on an editor button. Giving permissions just to shortcutfoo is not enough. NoScript also shows airbrake.io, stripe.com, olark.com. I don't know what any of those are, so I'm not enabling them. So I cannot use your website, as cool as the premise sounds :/

In order: 1) exception tracking api 2) payment processing api 3) live, on-page chat tool noscript is cool and all, but those 3 above listed items are perfectly fine to permanently enable on all sites

I would argue that #3 would be one I'd like to have blocked. I've never had a situation where those "Hey! Wanna chat with a salesperson!?" boxes isn't annoying.

Re: Build muscle memory with your favorite editor

#117
Love the concept, however this is much like learning a language by learning to translate.

求 -> ball -> O (actual ball)

vs

求 -> O (actual ball)

Classic study vs immersion.

The implementation will be much harder, but for this to be effective show the manipulation, not the description.

Re: Build muscle memory with your favorite editor

#118

Neat.. kinda fun. One thing is you might want to allow people to configure the META key. I have Emacs set up so that the Command key is META, so all my muscle memory is ruined when trying to run through the drills. But I like the concept and might use it to increase my shortcut kung-fu.

Command key now works as META for Emacs. Thanks for the suggestion!

Re: Build muscle memory with your favorite editor

#120

This really didn't work for me. I found needing to parse the command ("Move backward a word") broke the memory that I have built up over 15 years of using Emacs. Instead of naturally moving backwards with a flick of the fingers, I had to concentrate on where each finger was and on the key I was pressing. I think the goal of this is great, but as it stands, I'm not convinced it is going to help. Given it aborted my na…

I agree - just did this for vim. I don't think "move to end of whatever" I know what outcome I want. I never "say" it in my head.

To elaborate a little, I'd like to see a "you are here":

http://i.imgur.com/fDYEJ.png

you want to be here:

http://i.imgur.com/ijn0g.png

type thing. Not sure if this would work for other editors.

Post reply on HN