Closed JugglerShu closed 12 years ago
I suspect that the current approach is reasonable. There are certainly projects that use the client/server approach (eclim) but for Eclipse I far prefer Vrapper which takes an approach much more like XVim. Other popular related projects are IdeaVim (Vim plugin for IDEA apps like IntelliJ, WebStorm, RubyMine, etc.), ViEmu (Vi emulation for Visual Studio) and jVi (for Netbeans), all of which also take a similar approach. It does seem a bit of a waste that so many projects seem to end up reimplementing Vim, but I'm not sure I have a great suggestion to fix that especially given the variety of languages these IDEs are written in.
I too am a proponent of the current approach. I think it's overall better to get all of the IDE + a little bit of Vim than to get all of Vim + a little bit of the IDE.
For instance, there is never going to be a way to get the Interface Builder across to Vim, so as soon as you have to use that you have to switch to Xcode anyway. Ditto for debugging.
Thanks for the comments.
I do not have any intension to do the vim server thing right now but want to keep it in mind because its usable at some point.
So lets keep gathering and storing knowledge if we can use any vim feature in some case.
Anyway I keep developing current one at the moment.
I use ViEmu at work which is what led me to look and see if there was something similar for Xcode (though now that I am helping develop on XVim I wish I had the ability to modify ViEmu because it has a couple quirks that annoy me, hehe). I also agree that the current approach seems reasonable because you get all the power of Xcode with the familiarity of Vim. The mix we have going is extremely useful. If we could get the same by using the client/server approach I'm all for it. It's just that I would hate to trade full Vim support for more limited Xcode functionality.
This issue is for discussing if there is better way to use Vim in XCode.
I do not have any concrete ideas but followings may be hints to think of other ways.