From c6da152e9a2d42d95bab82f4b690a4c835ba8c13 Mon Sep 17 00:00:00 2001
From: Jacek Generowicz <jacg@my-post-office.net>
Date: Sun, 8 Dec 2019 18:23:48 +0100
Subject: [PATCH] ;convert extant addon tests to shellrunner format 3

---
 tests/addons/addons.test | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/tests/addons/addons.test b/tests/addons/addons.test
index 0f0154cfe..271461a86 100644
--- a/tests/addons/addons.test
+++ b/tests/addons/addons.test
@@ -4,24 +4,24 @@
 # they always run the first hledger executable in PATH
 
 # 1. flags after an add-command are handled by the add-on
- PATH=$PATH:. hledger addon --help
->>> /hledger-addon/
->>>=0
+$ PATH=$PATH:. hledger addon --help
+> /hledger-addon/
+>=0
 
 # 2. add-on flags which are not also defined in the main executable are a problem
- PATH=$PATH:. hledger addon --addonflag
->>>2 /Unknown flag: --addonflag/
->>>=1
+$ PATH=$PATH:. hledger addon --addonflag
+>2 /Unknown flag: --addonflag/
+>=1
 
 # 3. hledger main executable ignores anything after -- (and hides the -- from the add-on)
- PATH=$PATH:. hledger addon --help -- --addonflag
->>> /hledger-addon/
->>>=0
+$ PATH=$PATH:. hledger addon --help -- --addonflag
+> /hledger-addon/
+>=0
 
 # TODO how to reliably ensure no addons but still find the hledger executable ?
 # 4. having no addons shouldn't break the commands list
-# PATH= ~/.local/bin/stack exec -- hledger
-#>>>=0
+# $ PATH= ~/.local/bin/stack exec -- hledger
+# >=0
 
 # ############################    issue 457    #####################################
 #                                                                                  #