| Age | Commit message (Collapse) | Author |
|---|
|
Moving across history moved to <c-j>/<c-k> to keep <a-u>/<a-U>
for selection undo/redo
This reverts commit e0d33f51b36c9f0be7ae2467dab455d211bbf561.
|
|
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
|
|
|
|
Now that it is, we get the following error when trying to execute
`test/compose/select-display-columns`
```sh
./enabled: 2: [: 4: unexpected operator
```
This commit fixes the enabled check
|
|
Tracking the line/column of each token takes a surprising big part
of the command parsing logic runtime and is only necessary when we
hit an error.
|
|
|
|
There's a bug in current line completion, fix it.
Signed-off-by: Tw <tw19881113@gmail.com>
|
|
When doing line completion, we previously used to not complete the line
if it had different indent to the potential completion.
This commit changes the behaviour to ignore indentation when completing lines.
|
|
This makes it possible to do :select `%val{selections_decs}` and to
correctly combine $kak_quoted with those.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #3194
|
|
|
|
Only fail if all selections are discarded.
Fixes #2841
|
|
Fixes #2857
|
|
This should make the use case exposed in #2836 implementable.
|
|
As discussed in #2836
|
|
Fixes #2829
|
|
Fixes #2761
|
|
Relying on general selection update code is error prone due to
diffing.
Fixes #2394
|
|
This will prevent hooks added by the parent hook manager to be
gathered, as was decided during the discussion for #2603
|
|
|
|
|
|
|
|
Fixes #743
|
|
Restore the unicode test case using that.
|
|
This reverts commit 6aa892ef49c3a7c67512ed42de8ce2f24e0c02ce.
|
|
|
|
Fixes #406
|
|
Overlapping selections on erase confuse the ForwardChangeTracker
and will confuse the user,
Fixes #298
|
|
|
|
|
|
|
