Key binding Conflicts

[ball-hayden]

Hi there.

A few of the emmet key bindings conflict with default atom key bindings for linux:

ctrl-down and ctrl-up are move line down/up. alt-shift-up and alt-shift-down are add-selection-above/below.

I don't know if there is a way to change atom to use it's defaults over a plugins, but not having these is driving me mad at the moment!

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5618891-key-binding-conflicts?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).

[Rowno]

Same here. If it can't be fixed I'll have to switch back to Sublime Text again. :disappointed:

[Trudko]

Package does define a lot of its own keybiding which at least for now IMO isn't good idea because of keybiding conflits. @Rowno @ball-hayden what you could do is re-set keybiding which you need in your keymap.cson. For example I had to do it for settings view, which I use a lot:

'atom-text-editor[mini]':
  'ctrl-,': 'settings-view:open'

[KyivJunta]

:+1: Emmet should have an option to suppress its keybinding. Dont know if there API for this, but keybinding is one huge problem with Atom plugins, including Emmet .

[Trudko]

@alekmych there is discussion about it already, so I am sure it will get addressed. https://discuss.atom.io/t/key-binding-hell/12075 https://discuss.atom.io/t/announce-search-all-keybindings/12755

[segphault]

:+1:

I don't want emmet to override basic text editing shortcuts like ctrl+w and ctrl+e. That's really not cool.

[tvanantwerp]

I just discovered that this is why I wasn't able to open atom's markdown preview pane via keyboard shortcut. I hope this issue gets sorted out.

[Yatoom]

Hey guys, I made a quick fix by throwing out all keybindings and reconfigured tab to shift + space. You can manually add keybindings you are missing. https://atom.io/packages/emmet-simplified.

[sirianni]

Wouldn't a simple fix be for the emmet keybindings to be scoped to HTML files only? Currently the keybindgs are registered with a very broad scope 'atom-text-editor[mini]'

[jonboiser]

@sirianni Have you tried changing the scope in keymap.cson? You're definitely right about the overly-broad scope. Even in a Haskell file, emmet keybindings will have precedent over everything else.

[sirianni]

Have you tried changing the scope in keymap.cson?

@jonboiser Based on my understanding of how keybindings work, in order to follow your suggestion I'd have to redefine every single emmet keybinding in my keymap.cson which is a pretty heavyweight workaround.

[gkatsanos]

or get Webstorm/PHPStorm. Everything works, out of the box. Worth every penny. I've already spent half a day trying to setup 2-3 shortcuts.

[sergeche]

have to redefine every single emmet keybinding

you can disable default shortcuts completely in package preferences and add only those you’re interested

[fwuensche]

@Yatoom solution was the best choice for me. If you're just using emmet's autocomplete feature, that's an easy way to go.