Only 1 of 3 registered commands triggers activation


#1

Like it says on the tin, only the atom-gist-dev:save-share command triggers my package to be activated for some reason. So until I run that command, the other two don’t run/work. Once that one is run, everything works as expected. What am I doing wrong?

activate: (state) ->
  @subscriptions = new CompositeDisposable

  @subscriptions.add atom.commands.add 'atom-workspace', 'atom-gist-dev:clone': => @clone()
  @subscriptions.add atom.commands.add 'atom-workspace', 'atom-gist-dev:save': => @save()
  @subscriptions.add atom.commands.add 'atom-workspace', 'atom-gist-dev:save-share': => @save(true)

Add another "toggle" function?
#2

Of course I finally figured this out right after posting. The culprit was a bad activationCommands key in my package.json. Correct version is below.

"activationCommands": {
  "atom-workspace": [
    "atom-gist-dev:clone",
    "atom-gist-dev:save",
    "atom-gist-dev:save-share"
  ]
}