Overriding Core key bindings

[hadronized]

I tried to override Core keybindings (ctrl-alt-p and ctrl-alt-[) but it doesn’t work. I use the unbound! and native! strings, none works :( Any idea?

Furthermore, ctrl-alt-p is bound to the package specs command, which I don’t give a heck. How could I disable that? Thanks!

[izuzak]

Have you tried using unset!? It would also be helpful if you could share the contents of your keymap.cson file so that it's more clear what you tried exactly.

Also, Atom version, OS version and similar information is always helpful.

[hadronized]

Atom 0.162.0, Windows 10 Preview, keymap.cson:

'.workspace':
  'ctrl-alt-p': 'native!'
  'ctrl-alt-]': 'native!'

[izuzak]

Can you share a screenshot of the output of the Keybinding Resolver when you hit ctrl-alt-p?

https://github.com/atom/atom/blob/master/docs/debugging.md#check-the-keybindings

[hadronized]

It resolves to both mine and the core one. I'll provide a screenshot later on.

[hadronized]

I can’t use any hosting image service (ffs internet provider…), then I’ll just paste the output here @izuzak:

(in green) window:run-package-specs  body    c:\…\win32.json
(in grey) unset!   .workspace    c:\...\keymap.cson

[hadronized]

Yeah ok, nvm, it’s a fucking hell. Going back to Sublime Text 3. I can’t even correctly override basic keybindings.

[izuzak]

@phaazon Sorry for the frustration -- I misunderstood what you were trying to do.

This works for me for completely disabling that keybinding (and not unsetting it from a specific selector):

'.workspace':
  'ctrl-alt-p': 'abort!'

[hadronized]

If I do that, I can’t use the key anymore, because on my layout, alt-gr is bound to &…

[hadronized]

Ok, seriously, why can’t I use `ctrl-alt-]' (which is located at w on my azerty keyboard)? It does nothing while it should output a``. :(

[winstliu]

There's a known bug where Atom can't handle international keyboards (especially ones that have a special AltGr). See more at atom/atom-keymap#35 (AltGr) and atom/atom-keymap#37 (international keyboards).

[izuzak]

Sorry, I wasn't aware you were using a different layout. As @50Wliu mentioned, you're probably hitting atom/atom-keymap#35 and atom/atom-keymap#37. I'm closing this since the problem is already reported, but let me know if I misunderstood. Thanks for the additional information.

[hadronized]

Do you know when that will be properly handled?

[izuzak]

I don't know when that will be properly handled. The best way to get notified when that happens is to subscribe to those two issues.

[hanslivingstone]

For anyone else looking for an easier way, just created this package which automatically unbinds anything conflicting with what you set in 'keymap.cson': https://atom.io/packages/keymap-control

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!