-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undo after visual select doesn't behave like in vi #119
Comments
To figure out if it's a bug in Vintage or in Sublime's undo code, try the same steps using Sublime's standard undo instead of pressing |
If I replace the last two u's with cmd+z it does two undos, but still enters visual mode for the first undo operation. There's no difference between selecting the text using visual mode and shift + arrow keys. The problem steams from that 'u' in visual mode turns the text into lower case, but u when in command mode is undo. In vim, pressing the second u does NOT enter visual mode again whereas vintage does, so the 3rd press of u does not do undo but does a lower case operation again (ie same as the first u). So if you keep pressing u, you just go into an infinite loop between lowercasing the text and undoing the lower case operation in Vintage, but in vim you get undo operations after the first lower case operation. |
Closing this since it's the same as #120 which has one potential solution in it. |
Try the following:
In vi, these last three steps:
With this plugin you instead get:
So the selection is an undo level but shouldn't be. Any ideas how to fix this? Can I get the undo stack in some way?
The text was updated successfully, but these errors were encountered: