Go to settings > miscellaneous > and uncheck 'Stop cursor on error' That'll fix the issue and let you type properly.

I have to agree with bballard, this is incredibly frustrating, and had I not have read your comments I would have abandoned the site. Please make this the default - many people are used to typing this way.

This should really be the default and only setting. It's very annoying and incorrect otherwise.

It ignores keys that are incorrect, so pressing backspace isn't necessary and actually just delete the last character you typed correctly (Since that was technically the last key you typed if you don't count incorrect keys). There's a setting that make it take every key you type and just displays them as incorrect (And lets you backspace them as you'd expect), isn't not the default though.

You just "block" until you hit the correct key, so try to avoid pressing backspace at all and just focus on the correct key.

But that's not how real typing works...

I noticed something was weird about that, but I couldn't figure out the exact mechanic. Perhaps the intended lesson is to correct mistakes later (i.e. not now). This is how I was first taught years ago, even though it is not how I normally type things out now.

I very quickly hit that as well, and it took a few tries to figure out the behavior and why it was completely breaking my expectations.

Is it trying to approximate the correction-tape workflow from a manual typewriter?

Touch typing means you type the document, then correct errors, then apply formatting and font choice, and preferably don't make errors.

Maybe for typewriters, no way that math works out for fast typists though. This exercise indicates my time-cost-per-error is roughly equivalent to typing a word; the cognitive cost of leaving the site of the error can't possibly be lower than that.

It depends what and how you're typing.

It works for most of the traditional forms of typing (audio typing, typing from shorthand, etc) where you have a body of stuff that needs to be typed and not so well for stuff that programmers type where you're creating as you type.

You must check the text for errors when you've finished typing it so it makes sense to do all the error checking then. Some people find the cognitive focus switching of correcting errors as you type tricky.

Very good point. I think my argument still holds for brainstem-layer errors, where I know as I'm pressing the key that it's not what I meant-- it's hard for me to not correct those, anyway.

For the kind of typos that you would need to be watching the output to correct, it totally makes sense to batch those up sometimes.

I was under the impression touch typing was simply typing without looking at the keyboard, and instead watching the screen, where you can correct errors as they happen.

> I was under the impression touch typing was simply typing without looking at the keyboard, and instead watching the screen

Originally, it meant not looking at either the keyboard or the output (screen or, for an actual typewriter, the typed page) but only the source from which you were typing, if any -- it referred to typing accurately by touch alone.

It was a key skill when incorporating edits meant retyping, and looking at the output meant you couldn't also be looking at the source, and switching between the two had a significant productivity cost for a high-volume typist.

Its less critical of a skill today but still a useful skill to have if you need to reference some source document for information while typing, etc.