3 ms·

Thanks for the explanation, that makes sense. Good to know that states A and B are still accessible, I remember thinking they'd disappeared forever. Next time I

Thanks for the explanation, that makes sense. Good to know that states A and B are still accessible, I remember thinking they'd disappeared forever. Next time I try emacs (no doubt there'll be a next time!) I'll bear this in mind.

aasasd 6y ago
I'd consider using undo-tree instead. First, it might make more sense. Second, afaik Vim has about the same model (haven't used it in a while though). Undo-tree's navigation interface isn't a pinnacle of intuitiveness, however.
- dan-robertson 6y ago
  The tree in vim is weird and hidden. Basically there is an operation to go from a state to the state from which it was derived (“up the tree”) and an operation to go forward/backward in time (of state creation), which is basically navigation in changenum space. Ie if you make some changes: A -> B -> C -> D Undo: A -> B Make some other changes: A -> B -> E Then undo takes you up the ABE chain but if you use g- and g+, you navigate through the list ABCDE
  - aasasd 6y ago
    > g- and g+ Those are the operations, yeah! They went a long way for me. I think there's also a command or a third-party addon to see the undo states, in the undo-tree spirit—but surprisingly I've never needed it.