SonOfLilit wrote:
Why is a graphical IDE more "real" than a text editor with macros?
Not flaming, just asking what in full-blown IDEs you find more useful than
emacs.
It's just that lately I've moved to emacs for C++ GUI code, and that shows
that I can't find ANYTHING better in IDEs...
Aur
I never learned Emacs.
I consider myself an ultimate geek, and that admission alone will probably get me kicked out of the club.
But most of my career has been spent in industrial settings where the tools available were dictated. And when I did end up working with UNIX (BSD 4.2/4.3) "vi" was preferred over Emacs because Emacs was a memory hog. So I learned "vi" and today use "vim" and "Gvim". I *know* Emacs is the ultimate text editor and Lisp is the ultimate programming language -- I just never learned how to use Emacs and never had an opportunity to use Lisp and get paid for it. Then again, I never got paid to work in Forth either.
There's a better chance I might get paid to work in Ruby, though. And if so, I'll insist on a Komodo license, or maybe Sapphire in Steel. 
Speaking of Komodo in general and Komodo vs. KDevelop in particular, I downloaded the beta of Komodo Editor 4.0 and compared it with KDevelop for some "simple Ruby development tasks". KDevelop is, as I've noted before, an "industrial strength multi-language IDE" and is free as in freedom. The downside of KDevelop is that it is very intimately integrated with Linux, Qt and KDE. If you have different ideas about what an application should look like, you'll find yourself fighting the tool. And I think there are licensing gotchas that more or less constrain you to using KDevelop only for GPL projects.
The downside of Komodo Editor is that it isn't a full IDE, and it only supports scripting languages. But if all you're interested in is Ruby and portability is a concern, the Komodo Editor looks like a great tool. It's free as in beer and I think, though I don't know for sure, that it's "smarter" than Scite.
The full Komodo is limited only by the fact that it only supports scripting languages and is not free in either sense. It appears to be toolkit agnostic, although given that it supports Tcl/Tk, it's probably biased in that direction. It appears to be *much* easier to use when you want to import an existing CVS command-line project -- I tried for about two hours to import one of mine into KDevelop and couldn't get it to work. Komodo synced up with RubyForge as soon as I opened the directories, and it took me about five minutes to get the RSpec stuff to work, including the Rake task to run "rcov".
The only issue I have is that Komodo uses "/usr/bin/ruby" as the Ruby "command line interpreter", not "irb". I couldn't make "irb" work and I don't know why just yet.
The other criterion I'm looking at is the ability to handle new languages. As you may know, I do a lot of work in R, and eventually would want my IDE to work with R code. It looks like both KDevelop and Komodo are capable of being taught new languages, and it looks like the process is equally complex and detail-oriented for both tools.
And yes, Emacs has an excellent R interface, called "ess" (Emacs Speaks Statistics).
···
--
M. Edward (Ed) Borasky, FBG, AB, PTA, PGS, MS, MNLP, NST, ACMC(P)
http://borasky-research.blogspot.com/
If God had meant for carrots to be eaten cooked, He would have given rabbits fire.