The best way I've found it to work is the change the vsix file extension to zip, then copy the Emacs.vsk to my local Visual studio folder in AppData/Roaming (or Local?).... And then use a Keyboard Manager extension (by the same extension author) to recognize the "new" VSK.
This works about 70% of the time though.
I build developer tools and services at Microsoft (currently Codespaces, Live Share, IntelliCode) and maintain some OSS projects (CodeTour, GistPad, CodeSwing, WikiLens)
OK I apologize about this frustrating situation! I just sent an email to one of my peers to see if there’s any pro tips here, or if we’re considering native Emacs support. Stay tuned!
The author of the tool adapted it from a 2012 version.
The best way I've found it to work is the change the vsix file extension to zip, then copy the Emacs.vsk to my local Visual studio folder in AppData/Roaming (or Local?).... And then use a Keyboard Manager extension (by the same extension author) to recognize the "new" VSK.
This works about 70% of the time though.
OK I apologize about this frustrating situation! I just sent an email to one of my peers to see if there’s any pro tips here, or if we’re considering native Emacs support. Stay tuned!
Thanks so much Johnathan!
I was logged into the wrong account (which I deleted). Thanks again Jonathan. Have a great rest of your weekend.