If I select a line with
x followed by
X onto the next consequent line from the scratch buffer, or
x then delete, then
x again and delete the next line, and then if I were to
u undo what I had just deleted by any of the prior selections, the inherent visual selection of the former line as a result overtakes because - as I undestand it - this is the current implementation. See for example https://github.com/mawww/kakoune/issues/753#issuecomment-236429855
But this is hardly an improvement over vim.
[*]** this is a *scratch* buffer which won't be automatically saved *** *** use it for notes or open a file buffer with the :edit command ***
If, upon starting kak, the cursor is on the first character, then the expected behavior would be not to have - after going through an undo operation - the cursor before the newline
\n but rather on the first character, where it all started.
*** this is a *scratch* buffer which won't be automatically saved *** *** use it for notes or open a file buffer with the :edit command ***
I can safely say this hehe, nuisance, irks me to the point that the more I do it over and over again, the more I realized how sub-par the undo operation has become because of the way that visual selection with cursor and anchor work.
In other words, and loosely based on the example above, one would have to manually press
gh respectively, in order to keep up where the cursor was at, so it would better resemble where the
cursor was the undo operation would take off from the very beginning.
In this sense, the current undo, is not quite an undo. How could it be.