mirror of
https://github.com/mawww/kakoune.git
synced 2024-11-25 21:16:38 +03:00
e0d33f51b3
Whenever a new history node is committed after some undo steps, instead of creating a new branch in the undo graph, we first append the inverse modifications starting from the end of the undo list up to the current position before adding the new node. For example let's assume that the undo history is A-B-C, that a single undo has been done (bringing us to state B) and that a new change D is committed. Instead of creating a new branch starting at B, we add the inverse of C (noted ^C) at the end, and D afterwards. This results in the undo history A-B-C-^C-D. Since C-^C collapses to a null change, this is equivalent to A-B-D but without having lost the C branch of the history. If a new change is committed while no undo has been done, the new history node is simply appended to the list, as was the case previously. This results in a simplification of the user interaction, as two bindings are now sufficient to walk the entire undo history, as opposed to needing extra bindings to switch branches whenever they occur. The <a-u> and <a-U> bindings are now free. It also simplifies the implementation, as the graph traversal and branching code are not needed anymore. The parent and child of a node are now respectively the previous and the next elements in the list, so there is no need to store their ID as part of the node. Only the committing of an undo group is slightly more complex, as inverse history nodes need to be added depending on the current position in the undo list. The following article was the initial motivation for this change: https://github.com/zaboople/klonk/blob/master/TheGURQ.md |
||
|---|---|---|
| .. | ||
| pages | ||
| autoedit.asciidoc | ||
| coding-style.asciidoc | ||
| design.asciidoc | ||
| interfacing.asciidoc | ||
| json_ui.asciidoc | ||
| kak.1 | ||
| kakoune_logo.svg | ||
| screenshot-i3.gif | ||
| screenshot-tmux.gif | ||
| writing_scripts.asciidoc | ||
