Comment by godelski

  > There's no unified lexicon on cli tooling

While there isn't there is more than most people give credit to. It shouldn't be too much of a surprise giving cli people write cli tools getting inspiration from cli tools. I mean we can't even say there's a unifying language in the GUI space.

  > The real big brain approach here is to divorce the idea of vim from the command line editor and use it as a plugin in an IDE

Maybe I'll be convinced when a vim plugin or "vim bindings" represents something close to actual vim. I need a lot more than hjkl, gg, gG and such for movements. It's crazy how few even have H,M,L let alone <C-F>, <C-B>. I'm really surprised so many don't have / bit less surprised at * and the like. An ide giving me vim bindings needs to also give me :Ex, tabs, tags, and so on. I don't think I've ever seen a plugin give me :%s and I'd be really surprised if it gave me \\{-}.

I think there's a lot of confusion when it comes to vim. It's an editor. Editors aren't just for writing and the real power of vim is editing. It's a major bonus that I can do all this with less resource consumption that just a plugin

Frequently using vim bindings in plugins leads to me generating gibberish.

Frequently using vim bindings in plugins leads me to unintentionally closing windows