FixTabStops

[rebornix]

Yay! We love PRs! 🎊

Please include a description of your change & check your PR against this list, thanks:

• Commit message has a short title & issue references
• Commits are squashed
• It builds and tests pass (e.g gulp tslint)

Since this configuration is not accessible in vscode 1.0.0, we can't write test cases for it currently. So I just tested manually for now. A proper workaround is adding a test folder for testing (mentioned this before with @johnfn ) or waiting for VS Code's July release.

[rebornix]

Fixes #448.

[johnfn]

Fix the merge conflicts and we should be good to go.

The more of the VSC insert algo that we replicate inside InsertInInsertMode, the sadder I get. Those API extensions can't come soon enough. 😛

[rebornix]

Fix conflicts. It's almost the first thing I need to do after I wake up every day :)

I have a bad feeling about VSC stuff as well. While fixing bugs for CJK and a few other bugs, I found these bugs only exist in our code base but not am-vim or Alex's Vim prototype, and that's because we are handling the cursor position ourselves while they are delegating Insert/Delete in Insert Mode directly to VS Code. Not sure if there will be other hidden problems about the cursor problem any more but if it happens again, I'd like to further investigate.

[johnfn]

Unfortunately the cursor tracking is necessary for a number of things we do that amVim and the other Vim prototypes don't do - the most notable of which is history tracking.

[johnfn]

Sorry about making you fix all the conflicts though haha. If only this project wasn't so active... sigh... 😉