in reply to Professional Toolkits <=> vim + shell

> vim + shell + perldoc

You missed google!

On a more serious note, one disadvantage of "integrating" your development environment is that you lose (or sideline, anyhow) the flexibility and power of the shell.

I'm also a big fan of using one editor - in my case vim - for everything. So I use my editor for developing perl, ruby, php and java but also for email and for drafting documents (they go into openoffice if they need to look pretty).

I guess if you're wroking on a project that'll involve pair programming it'd be pretty important to have a standardized setup of editor/shell or IDE. Even if that meant having to not use your favourite editor/IDE. Does anyone have any experience of getting agreements on tools - I imagine its a herding cats type situation!
  • Comment on Re: Professional Toolkits <=> vim + shell

Replies are listed 'Best First'.
Re^2: Professional Toolkits <=> vim + shell
by wazoox (Prior) on Apr 06, 2006 at 16:51 UTC
    In my office we're two working with nedit, and two working with emacs. No problem so far...