IDEs (Was: Mainstream D Programming)

[BCS]

Reply to Peter,

> Some of these features can be accomplished with a powerful text
> editor, especially with the addition of suitable macros, plug-ins, or
> third party tools (that are invoked from inside the editor, of
> course). For example, Emacs together with the etags program can
> implement the "Go-to definition (even across files)." I actually do
> this quite regularly.
> 
> Considering how programmable high end editors are, I suppose in the
> long run there isn't necessarily much difference between an IDE and a
> text editor. For example: jEdit has a plug-in that will do XML
> validation. Who needs an XML development IDE? Except that jEdit really
> *is* a kind of XML development IDE (with the plug-in added).
> 
> My $0.02... IDEs are cool and I use them. But strangely at the end of
> the day I find myself doing most of my editing in Emacs. Why? Because
> Emacs works the same on all platforms, works on all text files, and
> can be extended to do all sorts of interesting things when and
> necessary. As weird as this sounds, I sometimes use Visual Studio to
> manage the build of my C++ programs while editing their source in
> Emacs in a separate window. (I do this because out-of-the-box Emacs
> knows how to word wrap comments in C++ comment blocks... a feature I
> can't live without).
> 
> Peter
> 

 I once saw a screen shot of IRSSI (an IRC chat app) running in a VS tab. 
I wonder what it would take to run emacs/vi as a VS plugin.