activate granular CSS scope for keymap by trigger command
alpha
atom-workspace
, atom-text-editor
or atom-pane
.config.cson
config.cson
to add configuration.submode.submode
object..
and each segment classname is added to target element.
after-save
submode, atom.workspace.getElement().classList.add("after-save")
after.move
submode, atom.workspace.getActiveTextEditor().element.classList("after", "move")
submode:submode:"after-save": # submode nametarget: "atom-workspace", # Must be one of ["atom-workspace", "atom-text-editor", "atom-pane"]commands: ["core:save" # List of commands which trigger this submode],"after.move":target: "atom-text-editor",commands: ["core:move-up""core:move-down""core:move-right""core:move-left"]
keymap.cson
# after you invoke `core:save`, you can invoke `some:command` by keystroke `a`'atom-workspace.after-save':"a": "some:command"# after you invoke `core:move-up/down/right/left`, you can invoke `some:command` by keystroke `a`'atom-text-editor.after.move':"a": "some:command"
g t t t t
...(each t
select next-tab
).g T T T T
...(each T
select previous-tab
).config.cson
and keymap.cson
.config.cson
submode:submode:"gt-mode":target: "atom-pane"commands: ["vim-mode-plus:next-tab" # `g t`"vim-mode-plus:previous-tab" # `g T`]
keymap.cson
'atom-pane.gt-mode':'t': 'vim-mode-plus:next-tab''T': 'vim-mode-plus:previous-tab'# To win over default `t`(vim-mode-plus:till) in text-editor scope.'atom-pane.gt-mode atom-text-editor.vim-mode-plus':'t': 'vim-mode-plus:next-tab''T': 'vim-mode-plus:previous-tab'
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.