Earlier quoted context omitted.
wow, thanks for Vrapper... this is great!
Fwiw, if you find yourself wanting a Vim plugin for just about any piece of software but don't know if it exists or not, just assume it does and google it.
The problem with vim
81–90 of 90 posts
Re: The problem with vim
#82Personally, this is why I limit my usage with vim with the core vim(to me it means vim-as-out-of-package-or-gvim-package), my customimzed .vimrc, and highlighting plugin. The original vim alone is more than enough to satisfy my needs, and it's compatible with virtually every machine that I'll be using after all. I can venture on plugins for more convenience, but I already have an ample satisfaction and I would rather…
If you use Firefox, I recommend the It's All Text! plugin, which opens $EDITOR in a new window and seamlessly transfers its contents into the textfield you care about. I think a Chrome version is in the works, but there's nothing releasable yet.
Re: The problem with vim
#83Earlier quoted context omitted.
If you use Firefox, I recommend the It's All Text! plugin, which opens $EDITOR in a new window and seamlessly transfers its contents into the textfield you care about. I think a Chrome version is in the works, but there's nothing releasable yet.
I use vimium for chrome; it's wonderful.
Re: The problem with vim
#84Recently I was studying Programming Languages Theory with Racket (using this book - http://cs.brown.edu/courses/cs173/2012/book/ ) and I didn't like DrRacket. So I decided to use Racket with Vim, but the only way could do it was through GNU Screen and Slime plugin for Vim. It works, but it takes several seconds for expressions to travel from Vim to GNU Screen and it is quite inconvenient. Furthermore, I don't have in…
Re: The problem with vim
#85Maybe there could be a Vim Users Anonymous or something.
Re: The problem with vim
#86If you are using vim with C# I highly recommend OmniSharp - https://github.com/nosami/Omnisharp It provides real intellisense, find usages, etc. It's based on NRefactory.
Re: The problem with vim
#87Earlier quoted context omitted.
> "libVim" I think it would be better for developers to allow their programs to launch external editors. That way users can pick whichever editor they like. All the developer has to do is create a temporary file, run a command to open it, and watch for changes. (Thanks to vimperator, I am using vim to write this.)
That would not enable you to use editor features like autocompletion, context awareness, etc. Now, you could also implement them in the external editors, but then you'd be at step one again and re-implement an IDE in vim.
Re: The problem with vim
#88Most of these vim emulators are open source, so there's always the chance to just fix it and do a pull request. The main two vim emulators that I am using are: - XVim for XCode - Evil for Emacs And both do a really good job. Evil beats XVim hands down, but XVim is a lot better than the others I tried: IdeaVim (for Intellij), Vrapper (Vim for Eclipse), and Vintage (Vim for Sublime). Out of these, vintage is by far the…
I agree that Vintage is pretty useless. I would recommend Vintageous[1] which has implemented far more bindings. Although annoyingly, it does not have :w, which I use quite often. [1] https://github.com/guillermooo/Vintageous
Re: The problem with vim
#89Most of these vim emulators are open source, so there's always the chance to just fix it and do a pull request. The main two vim emulators that I am using are: - XVim for XCode - Evil for Emacs And both do a really good job. Evil beats XVim hands down, but XVim is a lot better than the others I tried: IdeaVim (for Intellij), Vrapper (Vim for Eclipse), and Vintage (Vim for Sublime). Out of these, vintage is by far the…
For info, you can map jj to in .vrapperrc (or _vrapperrc). Maybe they added that after you tried it.
Re: The problem with vim
#90It takes a considerable amount of effort to learn vim. It takes twice as much to unlearn it.