Domain: satokar.com
Stories and comments across the archive that link to satokar.com.
Comments · 18
-
Re:Replacement
you didn't mention what the plugin was for eclipse
Indeed, I didn't. It's viplugin. It has some quirks including;
marks work but lose their position when you ad or remove lines (c)hanging a (w)ord when using a middle paste dosen't remember the change when you iterate a search and then do a . (repeat last command)
you can't paste into a command buffer (annoying)
some of the vi functions I mentioned don't work
It mostly works which is weird considering the vi plugin for vs works better.
-
A useful vi Plugin for Eclipse
If you use Eclipse, then you have to checkout http://www.satokar.com/viplugin/ it's a vi editor plugin for Eclipse. I've been using it for a year and their most recent version is very, very stable.
-
Re:Vim is painful.
-
Re:differences?
-
Plugins make Eclipse what it is
I've been using Eclipse for quite some time now, and must say that it's by far the best IDE I've ever had the pleasure of operating. Because of superior modularity, I can use different Plugins to simultaneously edit projects in C++, Perl, and Fortran with full syntax highlighting and real-time error checking. This saves alot of time in recompiling your apps!!!
The most important thing to me in moving to Eclipse was that it would fully support the Vi command set. There were several different Vi-type plugin options available, but after trying them all I ended up using the only commercial download of the bunch, which was availble for $20 here:
http://satokar.com/viplugin/
The only other IDE I've ever found that was acceptable before Eclipse was Visual SlickEdit, which had most of the same features as Eclipse but was very expensive and didn't have the F&OSS plugin community of Eclipse.
Now that I'm into Eclipse, I don't think I'll ever look back!
-Will the Chill
*please insert 10 cents for one additional sig* -
Re:What does this have to do with Vi?
Actually, just yesterday I was praying for VI key bindings for eclipse.
There is a quite decent vi plugin for Eclipse (payware, but worth it if you don't want to fight your muscle memory.) -
Re:RMIT CS
except for Eclipse, which they've started teaching to the newbies for some reason (much to the annoyance of the old guard.
Appease them with this http://www.satokar.com/viplugin/index.php :) ) :P -
Re:Please help me with vim
I found a vi plugin for Eclipse a while ago, it emulates almost of all vi's features in Eclipse, and it's very handy. The only problem is that it costs money and the trial has an idiotic nag screen that pops up like every 45secs, but i thought it was worth every cent when i bought it. http://satokar.com/viplugin/index.php
-
Re:Please help me with vim
-
Re:Vi with Eclipse
I use viPlugin with Eclipse. I'm a happy camper.
-
For those that like the best of both worlds
-
Re:Vim? Emacs foreva!Emacs, OTOH, has a keybinding style that translates great to other apps. GNU apps all use emacs keybindings (I wonder why), and even IDEs like eclipse have compatibility modes. I'm glad I'm not a vi user because I know I would never be able to get things done in GUI programs like eclipse.
Vi plugin for the Eclipse editor: http://www.satokar.com/viplugin/
Anyway, if you use a GNU system like Linux, you should learn emacs. Bash (readline), info, etc. all work just like emacs. It will really save you time and effort when every app uses the same keystrokes. C-t is a great timesaver in both bash and emacs.
Glad you realized you can use emacs keystrokes on bash. This doesn't mean much for emacs though. Bash allows for either emacs or vi keystrokes to be used. Type "set -o vi" to get it it use vi keystrokes, complete with the two modes. "set -o emacs" (which happens to be the default) to use emacs.
Also note, that while info might use keybindings similar to emacs, 'less', which is one of the most often used commands, uses vi keybindings.
Why doesn't vi let me go to the end of the line by pressing, say, end or going to the end of a shorter line and then pressing the up arrow? Irritating. I know a vi guru is going to explain how to do this now, but I don't really care about the answer.
Next time you don't really care about the answer, please do us a favor and quit blaming it on vi.
-
Re:Intellisense #1 feature, pay Bram to add itYou might want to give the viPlugin for Eclipse a try.
http://www.satokar.com/vipluginIt gives you Vi-like editing inside of Eclipse while retaining any and all Eclipse features. The two downsides are a) It's not free. But it's about $18 US, so if you're a Vi-nut it's a small price to pay... b) It's not actually Vi running in Eclipse... the author is recreating Vi's functionality to run inside of Eclipse. Because of this, it's not (yet?) feature complete and has bugs of its own.
Personally, I think it's (overall) fantastic. I use Eclipse for a wide range of languages... some of the language plugins combined with the Vi plugin make it the hands down best IDE for many languages for me, personally.
-
Re:Intellisense #1 feature, pay Bram to add it
viPlugin is a commercial (but cheap) plugin that adds a vim layer on top of standard eclipse editors. While it does have some bugs, problems with some editors, and doesn't do everything vim does, it does have the basic command, visual, insert mode functionality that I can't live without.
http://www.satokar.com/viplugin/index.php
This plugin + eclipse is super productive (for me, anyway) when writing java. -
Re:The IDE Issue...
You should check out the vi plugin at http://www.satokar.com/viplugin.
-
Vi for Eclipse
There is a VIM Emulator Plugin for IntelliJ IDEA.
There is also a Vi Plugin for Eclipse.
Also, KDevelop has happily embedded KVim for ages now.
Is that enough?
-
Re:Give it a try
Of course, someone has already made that:
http://www.satokar.com/viplugin/index.php
(and for the emacs-minded, eclipse can use different key-bindings, and an emacs one is provided...)
Wouter -
Re:Are they reinventing the wheel ?
Actually, it can do vi as well. The vi Plugin can be found here I'm not really a vi guy, though I can use it in a pinch, so I can't vouch for how usable it is for vi experts.