search

bulenkov / VSCodeKeymap4IntelliJ

25 stars 14 forks source link

Latest update broke custom configs #32

Open valtism opened 4 years ago

valtism commented 4 years ago

Just updated to Rubymine 2020.2 and it seems like my VSCode copy bindings have somehow been changed. They were originally derived from VSCode (MacOS), but now it seems to be my custom bindings, but applied to the Windows base.

pauldorehill commented 4 years ago

Same problem on CLion 2020.2

dmimat commented 4 years ago

Could you please check if the VSCode Keymap plugin is installed? (Preferences > Plugins) If not, installing the plugin and restarting the IDE should help.

pauldorehill commented 4 years ago

Ah... I just reinstalled and this time in the keymaps there are two...VSCode & VSCode (macOS)

dmimat commented 4 years ago

If you modified VSCode keymap, you can find the keymap file with your modifications in ~/Library/Application Support/JetBrains/<IDE><Version>/keymaps, it will be named VSCode copy.xml or something like this. Now if you see that your custom bindings are applied to the default keymap, you need to install the VSCode Keymap plugin, close the IDE, and then set the parent keymap to VSCode OSX in the root element - <keymap .... parent="VSCode OSX>. When you start the IDE, your custom keymap should work fine.

andymatuschak commented 4 years ago

I hit this issue this morning when updating, too. I've fixed the issue for myself, but if it's possible to resolve this issue in future updates, I suspect that will avoid many other disrupted mornings!