Timeline for Turn Vim's multiple undo history into git commits?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2022 at 19:39 | comment | added | D. Ben Knoble♦ | Let us continue this discussion in chat. | |
| Apr 8, 2022 at 18:36 | comment | added | Geremia |
@D.BenKnoble "In the second, we've lost A altogether." When using undo and redo, but not when using earlier and later. See Rich's comment above.
|
|
| Apr 8, 2022 at 13:06 | comment | added | D. Ben Knoble♦ |
I believe undotree() represents its branching via alt fields in the entries.
|
|
| Apr 8, 2022 at 13:05 | comment | added | D. Ben Knoble♦ | Consider this sequence: 1. Change line to A. 2. Undo. 3. Change line to B. Now, the undo tree has at least three nodes: the initial node, one from that to the change A, and one from the initial node to the change B (also the current the node). Linearized history would mean you write commits initial node <- A <- B. Only processing the current linear history would mean you write commits initial node <- B. In the first, we've lost the fact that A and B are in separate branches of the undo tree. In the second, we've lost A altogether. | |
| Apr 8, 2022 at 2:51 | comment | added | Geremia | @D.BenKnoble "either way some information is lost" No undo tree revisions (on only undo tree branch) between the current one and the file's first one are lost. "either it process the whole tree in some kind of linearized fashion, or it only process the linear history between start and now" What's the difference? | |
| Apr 7, 2022 at 21:28 | comment | added | D. Ben Knoble♦ | Agreed about git branches; what I’m looking at is that either it process the whole tree in some kind of linearized fashion, or it only process the linear history between start and now. So either way some information is lost, compared to plugins that show the entire undotree in a tree | |
| Apr 7, 2022 at 19:52 | comment | added | Geremia | @D.BenKnoble It makes Git commits with the whole undo tree from the current position in the tree. It does not make new Git branches to reflect undo tree branches. | |
| Apr 7, 2022 at 15:42 | comment | added | D. Ben Knoble♦ | This only does a single branch of the tree though, right? To get the entire graph would be harder | |
| Apr 7, 2022 at 8:47 | comment | added | Rich | Oh hey that didn’t turn out to be that much more complicated at all. Good job! | |
| Apr 6, 2022 at 16:49 | history | answered | Geremia | CC BY-SA 4.0 |