Acme has that neat feature of interpreting text as potential hypertext -- each of several addressing formats [3], when clicked, opens indicated file or resource, at the indicated point. Click on compiler error message and you get there. Prepare a command, click on it and you execute it. Etc., etc.
Also, unlike the mainstream IDEs and editors, those two work surprisingly well over network.
----
[1] http://en.wikipedia.org/wiki/Sam_(text_editor)
[2] http://en.wikipedia.org/wiki/Acme_(text_editor)
[3] implemented via http://en.wikipedia.org/wiki/Plumber_(program)
There are two main branches of Plan 9: the official, Bell Labs one [3], which is somewhat conservative (nonetheless the install iso is updated frequently), and 9atom [4], maintained by Erik Quanstrom, which has some more experimental features.
The core of the OS seems to be mostly established; both the 9P protocol (current version called `9P2000') that binds everything, several important fileservers and baseline libraries.
Probably the best is to look through contrib [5], which is where the userspace stuff is brewing.
Aside of the P9 proper, there is plan9port [6] maintained by Russ Cox -- collection of most of P9 utilities ported to generic POSIX environment (Linux, MacOS X etc.) [[and that's what I am using daily]] and 9vx [7] -- P9 ported to run in vx32 virtual machine.
In general, both classics like LaTeX and the newest, like Google's Go are ported to Plan 9 -- either natively, or, in some cases, through APE.
----
[3] http://plan9.bell-labs.com/plan9/
[4] http://www.quanstro.net/plan9/9atom/
[5] http://plan9.bell-labs.com/wiki/plan9/Contrib/index.html and http://plan9.bell-labs.com/wiki/plan9/Contrib_index/index.ht...
In my mind, if it's not background compiling your code as you type, it's not an IDE in the modern sense.
I doubt Linus thinks "compile while you type" is a good idea, I'm not sure how much further down you need to scale until it does become a useful feature.
Scripting languages don't need this though.
Did you miss the reason why we're compiling while you type? It's so that our IDE knows your codebase and can help you. It'll autosuggest things based on context rather than simply matching strings. It'll inspect your object model and stick in the right include directives for you. It'll let you rename things without having to search&replace&hope.
So yes, scripting languages do need this. At least if we're talking about things that your development environment needs to do to be considered a modern IDE.
I don't think this would be too difficult to write in vim, which has built-in auto-complete functions.
I think I first heard that from Tom Christiansen when he was heavily involved in the Perl community back in the mid '90s.
Even today, some of the most productive programmers I know only use X/Gnome/KDE(/OSX) as a means of organising terminals on modern hardware.