I really love Sublime and would love to continue working on building out language support packages for it, but there has been an outstanding bug that makes it unusable for long editing sessions. There appears to be a rather critical bug with how Sublime implements redo. Sublime prevents you from seeing which changes are being played forward/backwards in the undo stack. If you've ever wanted to quickly go back to a previous version of the file to recall which changes you've made, you'll have a very hard time because when you press undo/redo and changes are spread out across a large file, there's no way to see the change that you're replaying. You can see the before/after states, but you really want to see the actual change being applied (not currently possible with ST3 or ST2).
Here's the correct behavior (that vim and other editors use):
UNDO: Pops the last change off of the history stack, and moves the moves the cursor to the location where typing of that popped off change began.
REDO: Pushes a change back onto the undo stack, and moves the cursor to the location where the typing of that pushed change began.
This has been brought up before http://www.sublimetext.com/forum/viewtopic.php?f=3&t=9802#p38901
(the bug has existed for quite some time) and I keep hoping that one of the updates will fix this. I would greatly appreciate a fix, as it would make the Sublime editing experience usable enough for extended use. Would it be a relatively straightforward fix?