Reworked register variable

 - instead of dying, continues on
 - will revert if we find setup tasks being more useful, but it's causing contention with task groups. If this isn't sufficient, I'll need to figure out a different strategy.

alfred/alfred.go

@@ -212,8 +212,6 @@ func (a *Alfred) runTask(task string, args []string, formatted bool) bool {
 		// Register task output
 		if copyOfTask.Register != "" && copyOfTask.Command != "" {
 			a.Vars[copyOfTask.Register] = copyOfTask.Exec(copyOfTask.Command)
-			// No need to continue on ... return
-			return true
 		}
 
 		// Test ...

alfred_test.go

@@ -329,7 +329,7 @@ func TestTaskMultiArguments(t *testing.T) {
 }
 
 func TestRegisteringVariables(t *testing.T) {
-	sut, _ := run("alfred fourty.two", t)
+	sut, _ := run("alfred fourty.one", t)
 
 	if !strings.Contains(sut, "The variable is 5678") {
 		t.Logf("Expecting 5678 to be returned")

examples/demo-everything/.alfred/part-two.alfred.yml

@@ -11,9 +11,9 @@ fourty.one:
     register: my.new.var
     command: |
         echo "5678"
+    ok: fourty.two
 
 fourty.two:
-    setup: fourty.one
     summary: Retrieve a registered variable
     command: |
         echo The variable is {{ index .Vars "my.new.var"}}
@@ -24,4 +24,4 @@ fourty.three:
 
 fourty.four:
     summary: A task with two params
-    command: echo {{ index .Args 0 }} {{ index .Args 1 }}
+    command: echo {{ index .Args 0 }} {{ index .Args 1 }}