> Editors that make me take may hands off the keyboard in order to click around in the gui to move around my files are productivity killers. A couple thoughts

> Editors that make me take may hands off the keyboard in order to click around in the gui to move around my files are productivity killers. A couple thoughts on that: 1. Allowing you to take your hands off the keyboard in order to click around in a GUI is not necessarily the same thing as making you do it. Even in Visual Studio experienced users' hands tend to stay put. For example, to open up a file to see some other element's code, there's no sense in bothering with the mouse. Not when with a single keypress you can jump not only to the correct file, but to the correct position within that file. 2. On the other hand, needing to consult the manual in order to find out how to do something is often more time-consuming than mousing through a menu. In a well-developed GUI, mousing through a menu is also the quickest way to figure out a new keyboard command. Much quicker than Googling or digging through manpages. 3. Even if you haven't bothered to learn the keyboard commands for your graphical editor, if you're switching what file you're working in frequently enough that the fraction of the second it takes to click on a tab is adding up to anything remotely significant, then you've probably misplaced the blame for your productivity issues. If you're switching files that much, the amount of time you're wasting on mental context-switching is probably immense. Naturally all this assumes that one is using a well-designed graphical text editor, and sadly the vast bulk of graphical text editors simply aren't anywhere near as refined as emacs or vim. Especially not if you need one that's cross-platform. But let's be careful not to make radios out of coconuts here: The reason emacs and vim are so effective is because they are venerable, not because they are textual.