Shared publicly  - 
I hate those annoying UI errors you make that compound themselves.

Like you type a command in a shell. And then you want to redo the previous command. You need to cursor up twice to get it from your history. But accidentally you cursor up once and hit return. To correct yourself you now cursor up twice and hit return. But because of the mistake, the command you wanted is now three lines up and you do the wrong thing again. So you cursor up three times... All this is done automatically by your fingers and you have to cycle a few times before your conscious mind gets the message and you realise you need one extra cursor up.

Update: I forgot to mention the other example I meant to include. Something similar happens with task switchers in multitasking OSes. Make a single mistake with "double-home" on iOS or "alt-tab" on MacOSX and you may find yourself repeating it many times over.
Gershom B's profile photogwern branwen's profile photoRicardo Massaro's profile photoNoah Easterly's profile photo
This is my exact experience with the shell during my edit-compile-test cycle. Every damn time.
I tend to use C-r and use search to bring back things from history. It's a bit more reliable and you get instant feedback as you type.
+Johan Tibell Nice tip which I may make use of. Though I'm not always a fan of feedback. If you need to examine the screen do decide what key to type next then you've slowed down your work and you certainly can't exploit a typeahead buffer.
And there's (in the shell) !foo

Still, this happens a lot to me. In GHCI, too.
This is exactly why I've moved to a exclamation-point-centric shell workflow: "!m" instead of up-arrow-to-find-"mk", etc. Of course, when you're compiling using "mk" and also running "maya", my little workflow starts to accrue cost.
That's one reason I like zsh - the history ignores adjacent identical commands, so the second time (when I hit up up), I'd get what I wanted.
The differences in behavior between unix/bash and windows/cmd make this especially disconcerting and terrible and confusing.
+Ricardo Massaro Cool! I don't consider myself enough of an expert user of shells to recommend one over another. I was lucky and inherited a good zshrc.
Add a comment...