A current limitation of the original version, is that it requires the copying of a "vsk" file, into the Visual Studio product folder, which requires running the extension installer as administrator.
To solve this, my next check-in will instead make use of the Visual Studio import/export bindings (vssettings), stored per user, with a specified set of Emacs key bindings, that can then be edited locally according to taste.
A current limitation of the original version, is that it requires the copying of a "vsk" file, into the Visual Studio product folder, which requires running the extension installer as administrator.
To solve this, my next check-in will instead make use of the Visual Studio import/export bindings (vssettings), stored per user, with a specified set of Emacs key bindings, that can then be edited locally according to taste.