News for hackers. Stuff that matters.
Re:Why, oh why, do those nutheads use vi? (2007) by je42 on Sunday April 12, 2015 @09:42AM (#9363318)
* No tabs.

-> multiple vim plugins provide really confortable tabs.

* No project structure.

-> plugin. if you want that kind of tree next to your editor. (i.e. Nerdtree)

* in my IDE (eclipse based or intellij based) I can ctrl-click a class/object/other to navigate into that object's definition

-> tag search plugin. Haven't played with it much though.

* in my IDE I can search for classnames, I can press ctrl-T to find who inherits from something, ctrl-alt-H to find who uses something etc...

-> I believe there are some plugins for but here i haven't seen anything good so far.

* auto-complete(with annotation to tell you what the function variables are)

-> you complete me. plugin.

* debug inside your IDE

-> good point. have to wait for Neovim for this - I believe. Installing current WIP version from neovim is on my todolist. ;)

* run code-lint, auto-build on typing to detect errors, etc...

-> syntastic.

* auto refactor (I.E. extract method, move variable, extract class etc...)

-> good point. don't know any good plugin.

* format all your files according to your pre-specified project guideline.

-> plugin.;)

* sharing you IDE configuration with other contributors

-> here truly most IDEs suck. For vim you find lots of shared vimconfig on github.

* showing when files are/aren't in version control and integrating version control so that you view history in your IDE.

-> if you need to do in the editor... there is plugin for that. However, i found git command line is usually find. and for more serious committing I use GitX (L).

Re:Why, oh why, do those nutheads use vi? (2007) by MetaCosm on Sunday April 12, 2015 @05:20PM (#9364773)
> * in my IDE I can search for classnames, I can press ctrl-T to find who inherits from something, ctrl-alt-H to find who uses something etc...

>> -> I believe there are some plugins for but here i haven't seen anything good so far.

Language dependent, Go has "Oracle" for example, for finding callers, etc.

> * debug inside your IDE

>> -> good point. have to wait for Neovim for this - I believe. Installing current WIP version from neovim is on my todolist. ;)

Clewn.

> * auto refactor (I.E. extract method, move variable, extract class etc...)

>> -> good point. don't know any good plugin.

Language specific, Go has multiple and lots of people write small bits of script to do this -- but it is a place IDEs are far ahead of Vim.

> * showing when files are/aren't in version control and integrating version control so that you view history in your IDE.

>> -> if you need to do in the editor... there is plugin for that. However, i found git command line is usually find. and for more serious committing I use GitX (L).

Nerdtree & git-nerdtree.

Re:Why, oh why, do those nutheads use vi? (2007) by weaksauce on Sunday April 12, 2015 @10:19AM (#9363407)
I used to use Gitx but source tree is considerably better.
Re:Why, oh why, do those nutheads use vi? (2007) by je42 on Sunday April 12, 2015 @12:59PM (#9363941)
i found source tree to be very slow for the repositories that I have to deal with. GitX (L) dealt with them much better.