Yes, I get that. Funny, I actually do use Excel a lot to edit a lot of these things and don't think I could improve my productivity in any of them more than 10 or 20%. My real question is how much it would help me in the language I spend 80% of my time in(Python now), versus an IDE that was built specifically to help people writing Python.
But you make a good case and I'll probably go harder into emacs(I do use vim a fair amount now, and will try TextMate when I get that mac.
Things that emacs can do for most of the languages in that list (after you install some appropriate emacs modules) that I doubt Excel can do very easily:
Syntax highlighting (the emacs term is "font-lock"). Auto-indentation based on language syntax. Auto-completion of symbols based on the contents of open files (if you've defined a constant "MECHFISH" in a file, and you type "MEC" in another file and press a keystroke, the system fills in "MECHFISH". Press the keystroke multiple times to scroll through multiple possibilities.) Snippets (type "func" and press Tab; your editor inserts the skeleton of a function definition for you). Integration with your version control system (git, in my case). Navigate from one of two dozen open files to another without moving your hands from the keyboard. Browse directory trees in panes, picking out files for editing -- or run a shell command across a bunch of selected files. Search-and-replace using regular expressions. Recursive grep through directory trees (I use emacs igrep-mode for this.)
This is by no means an exhaustive list. So suffice it to say that if you can't get more than a 10% "productivity" improvement by swapping emacs for Excel, you must be one hell of an Excel power user!
Incidentally, don't spend too much time bouncing from vim to emacs to TextMate. These editors take time to learn. Pick one and focus on it. Read some blogs and some wikis. Get really good at your editor of choice.
How is that even possible? I'm not trying to be snarky or anything, I seriously want to know what your workflow is. It never would have occurred to me to use Excel for editing SQL queries; and as for Lisp or config file or HTML... how?
That explains the funny smell.
I wouldn't write my own editor until I had learned all three of those editors. After that... I still wouldn't write my own editor. ;) Spend your energy on a problem that urgently needs solving.
Now to your question: First, I can't answer it, because I'm not really a user of any IDE. Second, I think it is ill-posed. It's like asking which is more productive: using emacs, using Ruby, or using Excel. If you're an expert in one of these tools, you can use it to replace the others to some extent (I just encountered a programmer who was using Excel to compose hundreds of SQL queries. I have to admit that it works, although it would never occur to me to do this; I'd reach for emacs instead or, failing that, Ruby or Perl.) But, in general, these three tools are designed for different problems, and each tool has its sweet spot.
There are languages for which the vast majority of programmers use an IDE. (I'd probably use one if I had to do any Java programming; Mac development in Objective C might tempt me to use XCode to write code; I'm pretty sure .NET programmers use Microsoft tools.) But you become a different kind of programmer when you use something like emacs instead. For one thing, your text editor can be used to edit anything that is made of text: Python, PHP, Javascript, SQL, C, Ruby, Perl, Lisp, Haskell, Erlang, Java, shell scripts, config files, HTML, CSS, LaTeX, directory listings, version-control logs, long emails, documentation, outlines, to-do lists, blog entries, Wikipedia articles... ad infinitum. If you improve your emacs skills, your skill at editing all of these things increases. If a new language comes along, or a radical new way of using an old language, you needn't be one of those tiresome people who sits on the sidelines, complaining, because the New Thing lacks IDE support: You've got an editor that works fine with the New Thing, and which you already know how to use, and you can incrementally improve that editor by teaching it some New Thing macros, and before long someone (maybe you!) will write some emacs modes to support the New Thing.
Meanwhile, emacs skills do not become obsolete. The editor is quite possibly older than you, and will almost certainly live as long as you. It's cross-platform and open-source. Because it is not tightly tied to one language, platform, version-control system, workflow, or vendor, it has transcended and outlived all of these things.