Hacker News Reader

Comment by jrockway | Hacker News Reader

I just tried the same and had a very hard time typing gti. I had to slow down to get it; if I try to type it as quickly as possible I end up with either "git" or "gir". The parallization between hands just makes it too easy to type correctly. While your left pointer finger is making that long move from g to t, your right middle finger is already done pressing i.

I never type "sl" either.

View on HN

I was thinking along the same line.

When you use the same finger to type the G and T and a different finger to type I, it seems really impossible for me to accidentally type G-T-I.

The more common mistake is when you have to type two consecutive letters with the same finger but end up typing the next one earlier because its on a different finger (usually on the opposing hand).

Ex: 'teh' instead of 'the'- T,H with left index finger. E with left middle finger.

I also almost never type 'sl' though I do often type 'qw' in the Vim command line instead of 'wq'

A even more challenging task (at least for me) is to type a lower case letter after a symbol that requires Shift.

For example, I frequently type :Wq instead of :wq, especially in a SSH session, which adds some latency to the release of Shift key.

EDIT: SSH has nothing to do with this. It's just an emotional impact on the extra hassles of backspacing with latency.

Same here! It's true even if it's a capital letter. Like "HEllo", "BEst REgards", "THanks"...

About "git", for me left-index, right-middle, left-middle.

I do this all the time too, but I think you're wrong about the ssh difference.

ssh doesn't see the keystroke until it's fully formed by your OS and/or window manager, so there can be no latency to the release of shift.

Thanks for telling me that! I realized that I can make the same mistakes locally with comparable frequency. Perhaps it's just that I feel annoyed when I have to backspace with latency.

Use mosh instead: http://mosh.mit.edu/

It predicts what the server will do with your input and displays the result (with an underline) until the server responds. This means typing is always at local speed even if the network is being flaky.

Happens to me even when working directly in Vim on my local system. Earlier I used to map "Tabnew" to "tabnew" and other such hacks.

Then I saw this trick that saved me considerable grief:

    noremap ; :

Now, just hit ; in normal mode to get the command line.

Reply on news.ycombinator.com