You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the cause:
All mappings use arrow key movements (instead of function calls) to go to positions to be dot-compatible. virtualedit=insert makes it so that arrow key movement interacts with virtual text, but ultimate-autopair doesn't take this into account (and there is no easy way for it to take this into account).
The rest of the strangeness is because of how cmp works, which is outside of my curfew.
In your example, the keys that are used for the first fastwarp are <Del><Right><Right><Right><Right>" (+ some more which are non-relevant).
I will not be fixing this (in v0.6), as it requires a major redesign.
If you're fine with disabling virtualedit=insert, then that's one way of solving the bug.
The bug is already solved in v0.7-pre-alpha as the feature is added that makes it possible to configure how much dot-compatibility you want (though it is not yet public to the user), so you will be able to just set it to no-dot-compatible for fastwarp.
Screen.Recording.2024-07-26.at.12.47.54.mov
The text was updated successfully, but these errors were encountered: