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
I noticed a bug: when I move from a long line with cursor at, say, column 10, to a shorter line with length less than 10, the memorized largest horizontal cursor position will be "reset" to the horizontal position of the cursor on the shorter line, and will never come back to 10 after if the cursor is moved to a longer line.
To better explain the difference between the expected (default) behavior and the actual behavior, I make two screen recordings:
Expected behavior:
simplescreenrecorder-2023-03-31_15.25.43.mp4
Actual behavior:
simplescreenrecorder-2023-03-31_15.26.53.mp4
My suggestion is that it might be problem from setting window options on event CursorMoved, this can be considered as a vim bug, but currently it is possible to be effectively fixed by using winsaveview() and vinresetview(), to see why, please check the discussions here.
The text was updated successfully, but these errors were encountered:
Hi, thanks for your great work on this plugin!
I noticed a bug: when I move from a long line with cursor at, say, column 10, to a shorter line with length less than 10, the memorized largest horizontal cursor position will be "reset" to the horizontal position of the cursor on the shorter line, and will never come back to 10 after if the cursor is moved to a longer line.
To better explain the difference between the expected (default) behavior and the actual behavior, I make two screen recordings:
Expected behavior:
simplescreenrecorder-2023-03-31_15.25.43.mp4
Actual behavior:
simplescreenrecorder-2023-03-31_15.26.53.mp4
My suggestion is that it might be problem from setting window options on event
CursorMoved
, this can be considered as a vim bug, but currently it is possible to be effectively fixed by usingwinsaveview()
andvinresetview()
, to see why, please check the discussions here.The text was updated successfully, but these errors were encountered: