vim-seek

Very late responding, but some advantages are described here: https://github.com/goldfeld/vim-seek

Well since you mentioned long lines let me plug my own, because I find it a genuinely elegant solution to one related problem: http://github.com/goldfeld/vim-seek, it's a motion I created mostly to move around long lines, which were a major pain point for me especially when writing prose (and even more acutely painful back when I used soft-wrapped lines, though I still get a lot of mileage from it while using hard-wrap at 80 columns, RMS/Linus-style.)

All my programming life has been in higher-level languages, yet with Rust I'm being inexplicably drawn to down and dirty systems programming. It's cool to finally be able to use :make and all the C-oriented things like [i and ]i, ctags and the like. It's interesting seeing how much 'dogfooding' vim has in that tons of stuff are undoubtedly geared towards his own needs developing vim (and C applications in general.) Pretty much how I work with coding products, I work my best when I'm the use case, and great open source products like vi/vim and emacs excel in that legions of people share the creator's use case (and well, configurability right down to the bone.) I've found that a non-trivial amount of people do share the use case for the first project I've launched[1], I only hope for it to hold true for my most ambitious ones in the working

I was hoping someone would trash the idea of hjkl, which I personally don't like. So first I was disappointed to read yet again about not using the arrows. Then when I read the rest of the post, it definitely makes sense. I do use w, b quite frequently, and I don't use f, but I've found the vim-seek[1] plugin recently, and it seems to make more sense to use. It matches two rather than one character, which makes it much more precise. I think the bottom line is to move around to the right place and that going one character at a time is less efficient. Not so much whether this movement is via hjkl or the arrow keys. [1]https://github.com/goldfeld/vim-seek

There's actually a multi-cursor plugin for vim, http://github.com/paradigm/vim-multicursor, I know nothing of it's features but it speaks something of vim's extensibility. As for motions, what kind of motions do you think are difficult to create? I have dabbed in creating a fundamental new motion for vim which is analogous to f but takes two characters instead, and it does not rely on f's implementation to work. You can see it here http://github.com/goldfeld/vim-seek Regarding lack of context, I agree, but I can't say I've done enough vim plugin development to say whether I think it's beneficial or detrimental to vim to be limited so. Regions do actually sound like something with an infinite number of advanced and creative applications (stuff like Emacs org-mode). Do you know of editors that have such a feature? I'd be crazy for that.

I created vim-seek exactly for this reason, it's like f but takes always two characters, way faster than easymotion within the line (though I still use easymotion for longer distances) http://github.com/goldfeld/vim-seek