3 ms·
They've been making so much progress on the vim plugin. I was recently at a conference, and was talking to someone who works on Code. The conversation went some
by steveklabnik 10y ago
They've been making so much progress on the vim plugin. I was recently at a conference, and was talking to someone who works on Code. The conversation went something like this:
Me: "I wanted to use Code, but the vim integration wasn't good enough."
Her: "Oh yeah? What issues did you have, specifically?"
Me: "Let me just reinstall real quick and I'll show you."
Me: "... okay yeah this just works now. Awesome."
- tomdale 10y agoMost "vim emulation" plugins suck, because the vim way of thinking about things is so different from the typical GUI editor. Because of this, extension APIs often have to be wildly abused just to get even moderately decent parity with vim. Bugs and inconsistencies abound and are often impossible for the plugin author to fix. That's why it's been extremely heartening to see releases of VS Code that explicitly add extension points to enable features for the vim plugin[1]. It's not perfect now, but given that the VS Code team seems to be making it their mission to offer an extension API robust enough to make it perfect, I'm willing to deal with the quirks for now. [1]: https://code.visualstudio.com/updates/v1_5#_extension-authoring https://code.visualstudio.com/updates/v1_5#_extension-author...