Pressing `u` will undo all the stack.
<!-- For questions, ask us on [Slack](https://vscodevim-slackin.azurewebsites.net/) 👫. DONT CHANGE ANYTHING UNTIL THE -----. Thanks! --> * Click *thumbs-up* 👍 on this issue if you want it! * Click *confused* 😕 on this issue if not having it makes VSCodeVim unusable. The VSCodeVim team prioritizes issues based on reaction count. -------- **Is this a BUG REPORT or FEATURE REQUEST?** (choose one): This is a bug report <!-- If this is a BUG REPORT, please: - Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: - Describe *in detail* the feature/behavior/change you'd like to see. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --> **Environment**: <!-- Please ensure you are on the latest VSCode + VSCodeVim --> - **VSCode Version**: 1.15.1 - **VsCodeVim Version**: 0.10.0 - **OS**: macos 10.12.6 **What happened**: <!-- Exact keys you pressed. --> I press `u`in Normal mode in an editor window. Every single action in the undo stack was undone. Here's a GIF:  **What did you expect to happen**: I expected the last action on the stack to be undone. **How to reproduce it**: I have no idea. I was reliably triggering the bug with the exact buffer I had
Posted by yacinehmito on Sep 6, 2017, 8:07 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Pressing `u` will undo all the stack.
<!-- For questions, ask us on [Slack](https://vscodevim-slackin.azurewebsites.net/) 👫. DONT CHANGE ANYTHING UNTIL THE -----. Thanks! --> * Click *thumbs-up* 👍 on this issue if you want it! * Click *confused* 😕 on this issue if not having it makes VSCodeVim unusable. The VSCodeVim team prioritizes issues based on reaction count. -------- **Is this a BUG REPORT or FEATURE REQUEST?** (choose one): This is a bug report <!-- If this is a BUG REPORT, please: - Fill in as much of the template below as you can. If you leave out information, we can't help you as well. If this is a FEATURE REQUEST, please: - Describe *in detail* the feature/behavior/change you'd like to see. If we can't reproduce a bug or think a feature already exists, we might close your issue. If we're wrong, PLEASE feel free to reopen it and explain why. --> **Environment**: <!-- Please ensure you are on the latest VSCode + VSCodeVim --> - **VSCode Version**: 1.15.1 - **VsCodeVim Version**: 0.10.0 - **OS**: macos 10.12.6 **What happened**: <!-- Exact keys you pressed. --> I press `u`in Normal mode in an editor window. Every single action in the undo stack was undone. Here's a GIF:  **What did you expect to happen**: I expected the last action on the stack to be undone. **How to reproduce it**: I have no idea. I was reliably triggering the bug with the exact buffer I had
Comments (0)
No comments yet. Start the discussion.