The cool thing about it is that it even applies several layers deep. For example, òçfoo/dd<CR>ò the carriage return and second d would both be filled in. And if it's at the end of the program, the ò would be too
Or another cool example is the 6th line of my keyboard answer: ç^/Ùòf T|v,r_
For example, even if you have :nnoremap <C-s> :w!<cr>, pressing <C-s> still hangs the process because xterm intercepts it before vim has a chance to process it
These commands transform one set of keystrokes to another in some way, but I am somewhat fuzzy on which one is most appropriate for some situation. In addition, there are the ! variants of them as well. At the moment, my usage of them is pretty haphazard, so could I know what are the pitfalls ass...
> I am a little confused because I don't understand why this mode was created: all I can see is that it is less convenient than visual mode and doesn't provide more features.
But anyway, it means the mode that you enter when you call an operator and a motion is pending. So if you press d, vim sits and waits for a motion in o mode