Handle Ns and fix #684

[octref]

• Commit message has a short title & issue references
• Each commit does a logical chunk of work.
• It builds and tests pass (e.g gulp tslint)

[rebornix]

@octref do you mind rebasing against master to resolve the conflicts, others are perfect.

[jpoon]

Although, the commits can be squashed automatically by GitHub when we merge the PR, still good practice to squash commits to logical chunks of work.

http://programmers.stackexchange.com/questions/263164/why-squash-git-commits-for-pull-requests

[ThatRendle]

I will be very happy when this gets released. VSCodeVim is now good enough for me to be using Code as my primary editor. 🎉 😄

Pro Tip: I've started using GitKraken to do squashes with a helpful GUI (it's also very good for diff/merge).

[octref]

@rebornix @jpoon Done. Thanks for the tips!

@markrendle Thank you, I might look into it if it has good diffs. I'm good on CLI git for now.

[rebornix]

The failing test has nothing to do with @octref 's change so close/reopen it to trigger the CI again.

[jpoon]

Thanks @octref.

@rebornix, you should be able to restart the builds through Travis presuming Travis inherits the GitHub rights.

[rebornix]

@jpoon thanks for the info, don't know yet I have the power to manage Travis 💯 !