emacs. first job out of college, got put on a team that used emacs, so i learned emacs. things i love: non-modal interface (used vim in college, found myself f

emacs. first job out of college, got put on a team that used emacs, so i learned emacs. things i love: non-modal interface (used vim in college, found myself frequently cursing its modes: "do what i think, not what i type!"); lives on every system i work on; does not require smelling salts after encounters with large files; insanely flexible and powerful things i hate: insanely flexible and powerful (i.e., large investment required to capitalize on flexibility and power); i'm not a pianist (abundance of control and alt prefixes to key commands make rachmaninov cry from his grave); this is 2010 -- where is my anti-aliasing, dammit; after a year, i still have regular arguments with tabs/spaces/indentation to address your concern about navigating code efficiently, i sympathize. i felt that way when i started out (even after realizing i could select text with my mouse), but i'm in a phase where i spend more time thinking about writing code than actually writing it, so i worry less about how fast i can copy and paste an awkward selection from one file to another than i do about how well my editor fits with my work environment and personal habits.