Improve Undo/Redo

[iamntz]

Would be nice to have:

1. Persistent history. If you close/switch project (or editor), next time when you open undo should continue working.
2. Branched history. Let's say you write something, press undo, write something else, press undo. Now, when you press redo you should be asked wich history branch to use
3. Visual history (which basically is some kind of previous, but is displayed on request, not un redo)
4. Undo/Redo in selection only (with all previous points working)

All of these where present in the (defunct now) e-text editor

Related:

http://sublimetext.userecho.com/topic/92833-undo-trees/
http://sublimetext.userecho.com/topic/20126-undo-even-after-closing-and-reopening-file-storing-entire-undo-history/
http://sublimetext.userecho.com/topic/93082-undo-in-selection/

[vlakarados]

Don't see how 2-4 may be easily implemented, branching would be more of a headache but I don't mind. I wan't to link similar problems here: #107

As well as add that persistent history would be great if and only if files were always backed up on save so that when ST is closed, a change is made by another editor, when you open the file you may be able to undo that change. I think it's a killer feature as well as you may think of it as a diff glancing when you update to the latest revison from VCS.

[vovkkk]

Links from first message are dead.

Here is screen of mentioned visual undo of e text editor (just for those who never saw it before, like me)

[FichteFoll]

The History window is really something a proper VCS like git should provide. That's also compatible with a lot of other software.

[BenjaminSchaaf]

Undo history will be saved in the session with the next version. Other undo improvements should be separated into separate issues.

[FichteFoll]

Out of curiosity, how much of the history will be saved? I doubt it will be unbound.

[BenjaminSchaaf]

There's a fixed size limit per file, I think it's currently at ~2MB.

[BenjaminSchaaf]

Undo history has been added in 4075.