Corey Johnson & Nathan Sobo 84b2cabeb3 Calling .abortKeyBinding on an event that wasn't triggered by the keymap is ok ...

Certain events call `abortKeyBinding` to opt out of handling certain keybindings. Snippets does this with tab for example. If it's not a situation where it's appropriate to go to the next tab stop, we let the next binding be triggered, which could insert a tab, for example. But when we trigger events from the event palette, there *is* no next binding. Having a no-op function helps in this situation.

2012-10-19 12:42:27 -06:00

..

app

Calling .abortKeyBinding on an event that wasn't triggered by the keymap is ok

2012-10-19 12:42:27 -06:00

extensions

Display keybindings in EventPalette. Style a bit.

2012-10-19 12:02:00 -06:00

fixtures

If a TextMate syntax/preference fails to parse, catch error and log warning

2012-10-17 13:53:55 -07:00

stdlib

Only show events w/ descriptions in EventPalette

2012-10-19 11:24:40 -06:00

spec-bootstrap.coffee

Require atom.coffee in spec-bootstrap and benchmark-bootstrap

2012-08-30 11:26:31 -06:00

spec-helper.coffee

Optimization: Use absolute positioning instead of flexbox in editor

2012-09-25 14:58:31 -06:00

spec-suite.coffee

Move atom.resourcePath to window.resourcePath

2012-09-10 17:22:21 -07:00