My german keyboard didn't work :(
Typing Practice for Programmers
161–170 of 224 posts
Re: Typing Practice for Programmers
#162It doesn't appear to respect my keyboard layout - I'm using colemak (which works fine) but with UK symbols instead of US (which works everywhere else, including the HN comment box, but not in Typing.io where it wants me to type US symblos: eg " and @ are swapped).
Re: Typing Practice for Programmers
#163It seems like It is interesting. I wonder if I can learn to make fewer typos.
I had issues with the '-' character (for example, in the first line of the Shell Git lesson), and I'm just using the standard US keyboard layout. EDIT: also '_', as sp332 commented. Firefox on OS X.
Re: Typing Practice for Programmers
#164This doesn't seem to work with keyboard layouts that are different than US keyboards. My german keyboard didn't work :(
Re: Typing Practice for Programmers
#165Fun idea, but doesn't seem to recognize non-US keyboard layouts.
Thanks for the bug report. The next update will fix international keyboard layouts once I figure out the mess that is cross-browser, cross-language javascript key event handling:)
Re: Typing Practice for Programmers
#166Re: Typing Practice for Programmers
#167Re: Typing Practice for Programmers
#168Re: Typing Practice for Programmers
#169i really like it, but one thing disturbed me. why do you skip the comments?
Good question! I wanted to focus on helping users practice typing code with its often cumbersome symbols. The majority of comments are prose, comfortably near the home row, which I didn't feel deserved as much attention. Plus some comments (like the ones in the Guava projects) are longer than the code.
but valid point nevertheless.
Re: Typing Practice for Programmers
#170Earlier quoted context omitted.
Thanks, I'm glad you found the stats useful. In my initial version, I wasn't requiring the user to correct errors. I was personally getting errors rates around 3~5% , which appear good but seemed too low for the amount of errors I feel I make. Adding the need to backspace and correct keys revealed the true cost of mistyping a key, namely the wasted keys typed before correcting and all the backspaces. Thanks for point…
Supporting KILL and especially WERASE would be nice; I usually use one of those rather when I've made a string of errors, rather than watching and counting backspaces. And I agree with previous comments that it's hard to follow just how many backspaces are needed.
i use vim: so please support all vim movements. and the surround plugin. and while at it: my custom templating plugin as well :D.