Undo in Settings while changing vim.statusBarColors breaks the plugin

• 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.

BUG REPORT

Environment:

• VSCode Version: 1.15
• VsCodeVim Version: 0.10.0
• OS: Win 10

What happened:

Playing around with statusBarColors, I tried to go back to the last color after saving the settings file.
In the meantime, the automated colorCustomizations had already loaded, being undone instead and then auto-generated again.
I hit u a few times until I noticed, then escape a few times. Now this file is in a state where I cannot finish the current command. After closing the file and reopening (same vs code session), the command stack (see photo) is still there.

What did you expect to happen:
Esc should cancel whatever command I'm typing

How to reproduce it:
I guess hitting u and saving a lot while changing the status bar colors. Maybe some copy+paste, too.

Start by reproducing the behavior in the settings file while changing statusBarColors, saving repeatedly, and using undo, u, and Escape. Inspect the command stack shown in the report and compare the state before and after closing and reopening the file. Done means Escape reliably cancels the current command and reopening the file does not preserve a stuck command state.