Associates listener functions with commands in a
context-sensitive way using CSS selectors. You can access a global instance of
this class via
atom.commands, and commands registered there will be
presented in the command palette.
The global command registry facilitates a style of event handling known as
event delegation that was popularized by jQuery. Atom commands are expressed
as custom DOM events that can be invoked on the currently focused element via
a key binding or manually via the command palette. Rather than binding
listeners for command events directly to DOM nodes, you instead register
command event listeners globally on
atom.commands and constrain them to
specific kinds of elements with CSS selectors.
Command names must follow the
namespace:action pattern, where
will typically be the name of your package, and
action describes the
behavior of your command. If either part consists of multiple words, these
must be separated by hyphens. E.g.
All words should be lowercased.
As the event bubbles upward through the DOM, all registered event listeners
with matching selectors are invoked in order of specificity. In the event of a
specificity tie, the most recently registered listener is invoked first. This
mirrors the “cascade” semantics of CSS. Event listeners are invoked in the
context of the current DOM node, meaning
this always points at
event.currentTarget. As is normally the case with DOM events,
stopImmediatePropagation can be used to terminate the
bubbling process and prevent invocation of additional listeners.
Here is a command that inserts the current date in an editor:
'user:insert-date': (event) ->
editor = @getModel()
Add one or more command listeners associated with a selector.
Returns a Disposable on which
Find all registered commands matching a query.
An Object containing one or more of the following keys:
A DOM node that is the hypothetical target of a given command.
Simulate the dispatch of a command on a DOM node.
This can be useful for testing when you want to simulate the invocation of a command on a detached DOM node. Otherwise, the DOM node in question needs to be attached to the document so the event bubbles up to the root node to be processed.
The DOM node at which to start bubbling the command event.
String indicating the name of the command to dispatch.
Invoke the given callback before dispatching a command event.
Function to be called before dispatching each command
The Event that will be dispatched