Patch for issue #119

[quarnster]

Just realized it was very straight forward to get the desired behavior.

[quarnster]

Actually, this is still not quite. While pressing u multiple times now does indeed do multiple undo steps, pressing for example 'i' does not enter insert mode and x doesn't delete characters now, so something is still amiss.

[quarnster]

This is working now with commit 5e3909a :)

Please merge.

[michaelphines]

Thanks quarnster! This works great. I've been bitten by this more than once.

Holding u to undo and going back just a bit too far and then realizing that your redo buffer is empty is very sad.

[jordwalke]

Thanks you! Would love to see this merged.

[jordwalke]

Here's why this bug makes Vintage mode unusable. If you press "u", and enter visual mode, it is possible to hit another "u" and trigger a case change. This is horrible because it ruins your undo tree! Now you can't redo to recover where you were in the editing process. Does anyone know how to solve this with keymappings in the mean time?

[jordwalke]

@quarnster: You may want to amend the diff with support for Redo. #5e3909a fixes undo, but not redo.

[jordwalke]

In addition to the VintageUndo commit, I believe this needs to be added. Thoughts?

class VintageRedo(sublime_plugin.WindowCommand):
    def run(self):
        # Needs to be a window command as running the undo command while the
        # undo stack is being updated (like being inside of an edit in a
        # TextCommand) causes problems
        self.window.active_view().run_command("redo")
        self.window.active_view().run_command("exit_visual_mode")