* But, in real programming, you spend 80-90% of your time [...]* Well, yeah. But the question was about text editors -- how do you optimise that 10% of your ti

* But, in real programming, you spend 80-90% of your time [...]* Well, yeah. But the question was about text editors -- how do you optimise that 10% of your time when you're actually cutting code? My point was, ultra-terse command syntax like vi's don't amount to much if what you're really typing is; arr(<back>[3<back>2];<back> to get the string arr[2] into your source code. Also, typing matters more in dynamic languages or uncompiled source like html, where spelling mistakes can go undetected more easily. The real benefits, as you note, are in things like automatic intellisense-style function- and class-lookups, easy integration with source control and documentation and refactoring/lint tools, and ease of navigating the call graph. The big win, obviously, is live IE and firefox previewing ;) http://www.sublimetextwiki.com/cgi-bin/moin.cgi/BrowsersPlugin http://www.sublimetextwiki.com/cgi-bin/moin.cgi/BrowsersPlug...