Unable to activate the extension

[grantg-ht]

Hello there! I installed the Master Key extension and tried the Master Key: Activate Keybindings command as prescribed, but the only thing that happens is a little spinner with "Activating Extensions" next to it shows up in my status bar. It spins for about 5 seconds then disappears, but that's all. I tried looking for an error anywhere, but I didn't see anything for Master Key in the Output view, not even in any of the "Extension Host" output channels. Any clues on how to proceed?

My VS Code is fully updated, running on Windows 11. I get the same result trying this in workspaces both in WSL and in Windows.

[haberdashPI]

🤔 Very weird. I've never had this problem. My best guess is that something about how I'm handling paths is specific to unix...

I'll take a look and see if I can get this working on partner's machine when I get a chance (she has Windows on her laptop), and see if I can reproduce (and fix) the problem there.

[haberdashPI]

I've created an issue here #51

[haberdashPI]

Okay, I've done a bit of investigation. A few things I've learned

1. I can reproduce your problem when I installed VSCode on a windows machine. Should make this easier to debug 😌
2. I can still get the extension to work:
   a. after trying to activate the keybindings, close VSCode
   b. open it again and try again
   c. it will get further this time: you should be able to try and activate "Larkin" keybindings, but it will not completely work
   d. close VSCode again
   e. reopen it and try to activate the keybindings again, everything should work now 😬

I don't really understand why this fails the first two times, and for different reasons, or why just trying it again works. I can see some errors in the developer console that look like security issues: but if so, why does it work at all on the third try 😕

[haberdashPI]

With the latest release you can solve this problem in two ways:

• Run command "Developer: Reload Window"
• OR Close and reopen VSCode

Then call the "Activate Keybindings" command.

The README has been updated accordingly.

I have left #51 open, and will continue investigating this as I can to see if I can fully resolve the issue. However this workaround seems relatively straightforward to use so long as you know to do it.