===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
shelltestrunner-1.9/README.md-162-| format 1    | command first, exit status is required                                       | `(none) <<< >>> >>>2 >>>=` |
shelltestrunner-1.9/README.md:163:| format 2    | input first, can be reused by multiple tests, some delimiters can be omitted | `<<<    $$$ >>> >>>2 >>>=` |
shelltestrunner-1.9/README.md:164:| format 3    | like format 2, but with shorter delimiters                                   | `<      $   >   >2   >=`   |
shelltestrunner-1.9/README.md-165-
##############################################
shelltestrunner-1.9/README.md-223-
shelltestrunner-1.9/README.md:224:Two spaces between `$$$` and the command protects it from -w/--with.
shelltestrunner-1.9/README.md-225-
##############################################
shelltestrunner-1.9/README.md-227-Without it, input begins at the first non-blank/comment line.
shelltestrunner-1.9/README.md:228:Input ends at the `$$$` delimiter. You can't put a comment before the first `$$$`.
shelltestrunner-1.9/README.md-229-
##############################################
shelltestrunner-1.9/README.md-231-Expected output/stderr extends to the next `>>>2` or `>>>=` if present,
shelltestrunner-1.9/README.md:232:or to the last non-blank/comment line before the next `<<<` or `$$$` or file end.
shelltestrunner-1.9/README.md-233-`/REGEX/` regular expression patterns may be used instead of