rundoc 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1e570f8645e887ed3c6cfd9a93cfc5933b57734a
-  data.tar.gz: e6925f4cbcb8e5aa68711a6918e6d44ae0f2c788
+  metadata.gz: 7935527c5d717e2c4bdc0883a285dd3c7f834f65
+  data.tar.gz: ffc9bf341d82df737a5dc3ba4bb557160ae049b9
 SHA512:
-  metadata.gz: ee03707c8cf0eb97d92683b3f0d49ad6d296807c607b58e75cb4e420fbbbea09c78f89265d8a64d52f7979230e5d43d05502421ca80d9478f795c60a51f57ee6
-  data.tar.gz: edd4a92ac3c1bac6e6c210ab37788003e2de1310f9615e5b74ac448dcff1c710d89ee51ed38d806b752bb46d6808f26809bdbc27c1cf4d3371ba4caefb252c72
+  metadata.gz: e4839a376fc7911464bfd37ec2a64cc824963a52bef72d1e9e4876c07c8e1f5d6d1d99bab48243ef1c769cb98dabf186624dfe4ecf5a411480a6a748fd0293ab
+  data.tar.gz: 6cd4c38c55413efe85e174b561f39e99bc5788d21e2f63e93cef0c709563609a3864f704cb05c8c04b139d999ef789addeda7105b0b71c8f524890cc4aad2a4d

data/.gitignore

@@ -3,3 +3,5 @@ test/fixtures/*/tmp/
 test/fixtures/*/myapp/
 *.gem
 
+.DS_Store
+Gemfile.lock

data/README.md

@@ -1,12 +1,18 @@
-## Rundoc
+# RunDOC
+
+![](https://www.dropbox.com/s/u354td51brynr4h/Screenshot%202017-05-09%2009.36.33.png?dl=1)
 
 ## What
 
-Write more technical content, faster and with a better consistency by using rundoc. Write in a rundoc compatible markdown format, then run your docs to generate matching projects. Instead of writing a tutorial and then building an example separately, your documentation can build the example app for you. Not only does this keep your doc writing DRY, it also enforces consistency and accuracy. If you make a typo in your docs your project won't build...you'll get early warning and be able to fix it before it has the opportunity to confuse your reader.
+This library allows you to "run" your docs and embed the code as well as results back into the documentation.
+
+Write in a runDOC compatible markdown format, then run your docs to generate matching projects. Instead of writing a tutorial and then building an example separately, your documentation can build the example app for you. Not only does this keep your doc writing DRY, it also enforces consistency and accuracy. If you make a typo in your docs your project won't build...you'll get early warning and be able to fix it before it has the opportunity to confuse your reader.
+
+Think of runDOC as your ever-vigilant tech editor and writing partner.
 
-Think of rundoc as your ever-vigilant tech editor and writing partner.
+Once docs are run, they output a project and fully valid markdown doc (without any of the special runDOC tags). You could configure your project to be automatically pushed to github or anything else you want afterwards, check out the config section.
 
-Once docs are run, they output a project and fully valid markdown doc (without any of the special rundoc tags). You could configure your project to be automatically pushed to github or anything else you want afterwards, check out the config section.
+Write more technical content, faster and with a better consistency by using runDOC.
 
 ## Why
 
@@ -17,13 +23,13 @@ documentation at the same time. I enjoyed the experience but having to do both e
 While I was writing the course I dreamed of a system where the docs and the
 code could automatically stay in sync. One where if I had a typo in my tutorials, an automatic tech-editor would know and tell me. One where I couldn't accidentally skip over critical sections leaving true novices confused.
 
-Dream no more, because rundoc does just that:
+Dream no more, because runDOC does just that:
 
 Write docs, build software.
 
 ## Isn't this Overkill?
 
-No. Many new doc writers skip steps accidentally, or omit lines of code with `...` and assume their readers can follow along. Even if this is true for 80% of your users, 20% of people will become frustrated and may give up as a result. I found by including [check steps](http://schneems.com/post/60359275700/prepare-do-test-make-your-technical-writing-shine) such as running `ls` to ensure directory contents were the difference between good docs and great ones. The only problem: the output of `ls` on a Rails 4.0.0 and 4.0.1 project may be different. So the only way to ensure output is to actually run the command and copy it into your docs. With rundoc you don't need to do that. Rundoc runs the command then it can insert the output for you.
+No. Many new doc writers skip steps accidentally, or omit lines of code with `...` and assume their readers can follow along. Even if this is true for 80% of your users, 20% of people will become frustrated and may give up as a result. I found by including [check steps](http://schneems.com/post/60359275700/prepare-do-test-make-your-technical-writing-shine) such as running `ls` to ensure directory contents were the difference between good docs and great ones. The only problem: the output of `ls` on a Rails 4.0.0 and 4.0.1 project may be different. So the only way to ensure output is to actually run the command and copy it into your docs. With runDOC you don't need to do that. Rundoc runs the command then it can insert the output for you.
 
 If you don't intend on updating or revising your content, then this project is overkill. On the other hand if you're writing docs without the intent of revising them, you probably shouldn't be writing technical docs.
 
@@ -46,7 +52,7 @@ gem 'rundoc`
 Run the `rundoc build` command on any markdown file
 
 ```sh
-$ rundoc build --path rundoc.md
+$ rundoc build --path runDOC.md
 ```
 
 Note: This command will create and manipulate directories in the working directory of your source markdown file. Best practice is to have your source markdown file in it's own empty directory.
@@ -56,20 +62,19 @@ This will generate a project folder with your project in it, and a markdown READ
 ## Write it:
 
 Rundoc uses github flavored markdown. This means you write like normal but in your code sections
-you can add special annotations that when run through rundoc can
+you can add special annotations that when run through runDOC can
 generate a project.
 
-All rundoc commands are prefixed with three colons `:::` and are inclosed in a code block a
+All runDOC commands are prefixed with three colons `:::` and are inclosed in a code block a
 command such as `$` which is an alias for `bash` commands like this:
 
     ```
-    ::: $ git init .
+    :::> $ git init .
     ```
 
 Nothing before the three colons matters. The space between the colons
 and the command is optional.
 
-
 If you don't want the command to output to your markdown document you
 can add a minus symbol `-` to the end to prevent it from being
 rendered.
@@ -78,13 +83,13 @@ rendered.
     :::- $ git init .
     ```
 
-Note: If all commands inside of a code block are hidden, the entire codeblock will not be rendered.
+> Note: If all commands inside of a code block are hidden, the entire codeblock will not be rendered.
 
 If you want the output of the actual command to be rendered to
-the screen you can use an equal sign so that
+the screen you can use two arrows so that:
 
     ```
-    :::= $ ls
+    :::>> $ ls
     ```
 
 This code block might generate an output something like this to your markdown doc:
@@ -95,19 +100,29 @@ This code block might generate an output something like this to your markdown do
         Gemfile.lock  Rakefile  config    db    lib   public    test    vendor
     ```
 
-That's the syntax, let's look at different rundoc commands
+That's the syntax, let's look at different runDOC commands
+
+## Rendering Cheat Sheet
+
+An arrow `>` is shorthand for "render this" and a dash `-` is shorthand for skip this section. The posions two positions are command first and result second. You can skip a trailing `-`.
+
+
+- `:::>`  (yes command, not result)
+- `:::>>` (yes command, yes result)
+- `:::-`  (not command, not result)
+- `:::->` (not command, yes result)
 
 ## Shell Commands
 
 Current Commands:
 
 - `$`
-- `fail.$
+- `fail.$`
 
 Anything you pass to `$` will be run in a shell. Any items below the command will be passed into the stdin of the bash command so:
 
     ```
-    :::= $ tail -n 2
+    :::>> $ tail -n 2
     foo
     bar
     baz
@@ -122,12 +137,12 @@ Would output:
    bahz
    ```
 
-This could be useful if you are running an interactive command such as `play new` which requires user input. For more fine grained input you'll need to use a custom repl object (will be covered later).
+This STDIN feature could be useful if you are running an interactive command such as `play new` which requires user input. For more fine grained input you'll need to use a custom repl object (will be covered later).
 
 If a shell command returns a non-zero exit status an error will be raised, if you expect a command to fail you can run it with `fail.$` keyword
 
     ```
-    :::= fail.$ cat /dev/null/foo
+    :::>> fail.$ cat /dev/null/foo
     ```
 
 Even though this command returns a non zero exit status, the contents of the command will be written since we're stating that we don't care if the command fails. This would be the output:
@@ -142,14 +157,14 @@ Some commands may be custom, for example when running `cd` you likely want to ch
 
 
     ```
-    :::= $ cd myapp/config
-    :::= $ cat database.yml
+    :::>> $ cd myapp/config
+    :::>> $ cat database.yml
     ```
 
-However this command would fall on it's face:
+However this command would fall on its face:
 
     ```
-    :::= $ cd myapp/config && cat database.yml
+    :::>> $ cd myapp/config && cat database.yml
     ```
 
 These custom commands are kept to a minimum, and for the most part behave as you would expect them to. Write your docs as you normally would and check the output frequently.
@@ -164,10 +179,10 @@ Current Commands:
 - `file.append`
 - `file.remove`
 
-Use the `filewrite` keyword followed by a filename, on the next line(s) put the contents of the file
+Use the `file.write` keyword followed by a filename, on the next line(s) put the contents of the file
 
     ```
-    ::: file.write config/routes.rb
+    :::> file.write config/routes.rb
 
     Example::Application.routes.draw do
       root        :to => "pages#index"
@@ -181,7 +196,7 @@ Use the `filewrite` keyword followed by a filename, on the next line(s) put the
 If you wanted to change `users` to `products` you could write to the same file again.
 
     ```
-    ::: file.write config/routes.rb
+    :::> file.write config/routes.rb
     Example::Application.routes.draw do
       root        :to => "pages#index"
 
@@ -196,7 +211,7 @@ To fully delete files use bash `$` command such as `::: $ rm foo.rb`.
 To add contents to a file you can use `file.append`
 
     ```
-    :::= file.append myapp/Gemfile
+    :::>> file.append myapp/Gemfile
     gem 'pg'
     gem 'sextant', group: :development
     gem 'wicked'
@@ -206,7 +221,7 @@ To add contents to a file you can use `file.append`
 The contents of the file (in this example a file named `Gemfile`) will remain unchanged, but the contents of the `file.append` block will now appear in the bottom of the file. If you want to append the contents to a specific part of the file instead of the end of the file you can specify line number by putting a hash (`#`) then a number following it.
 
     ```
-    :::= file.append myapp/Gemfile#22
+    :::>> file.append myapp/Gemfile#22
     gem 'rails_12factor'
     ```
 This will add the `gem 'rails_12factor'` on line 22 of the file `myapp/Gemfile`. If line 22 has existing contents, they will be bumped down to line 23.
@@ -214,7 +229,7 @@ This will add the `gem 'rails_12factor'` on line 22 of the file `myapp/Gemfile`.
 Some times you may want to remove a small amount of text from an existing file. You can do this using `file.remove`, you pass in the contents you want removed:
 
     ```
-    :::= file.remove myapp/Gemfile
+    :::>> file.remove myapp/Gemfile
     gem 'sqlite3'
     ```
 
@@ -222,20 +237,19 @@ When this is run, the file `Gemfile` will be modified to not include `gem 'sqlit
 
 Note: `file.remove` currently requires a very explicit match so things like double versus single quotes, whitespace, and letter case all matter. Current best practice is to only use it for single line removals.
 
-
 ## Pipe
 
 Commands:
 - `|`
 - `pipe` (aliased `|`)
 
-Sometimes you need to need to pass data from one command to another. To do this there is a provided pipe command `|`
+Sometimes you need to need to pass data from one command to another. To do this there is a provided pipe command `|`.
 
 Let's say you want to output the first 23 lines of a file but you don't want to confuse your users with an additional pipe command in your shell line you could write something like this:
 
 ```sh
-:::  $ cat config/database.yml
-:::= | $ head -n 23
+:::>  $ cat config/database.yml
+:::>> | $ head -n 23
 ```
 
 Anything after the pipe `|` will generate a new command with the output of the previous command passed to it. The pipe command will only ouput its result, so the user will not know it was even executed.
@@ -245,7 +259,7 @@ This command is currently hacked together, and needs a refactor. Use it, but if
 
 ## Configure
 
-You can configure your docs in your docs use the `rundoc` command
+You can configure your docs in your docs use the `runDOC` command
 
     ```
     :::- rundoc
@@ -272,7 +286,7 @@ This will eval any code you put under that line (in Ruby). If you want to run so
 
 **Project Root**
 
-By default your app builds in a `tmp` directory. If any failures occur the results will remain in `tmp`. On a successful build the contents are copied over to `project`. If you are generating a new rails project in your code `$ rails new myapp`. Then the finished directory would be in `project/myapp`. If you don't like the `./project` prefix you could tell rundoc to output contents in `./myapp` instead.
+By default your app builds in a `tmp` directory. If any failures occur the results will remain in `tmp`. On a successful build the contents are copied over to `project`. If you are generating a new rails project in your code `$ rails new myapp`. Then the finished directory would be in `project/myapp`. If you don't like the `./project` prefix you could tell runDOC to output contents in `./myapp` instead.
 
     ```
     :::- rundoc
@@ -300,10 +314,27 @@ This command `filter_sensitive` can be called multiple times with different valu
 
 This is a section for brainstorming. If it's here it's not guaranteed to get worked on, but it will be considered.
 
-- Breakpoints?
-- Better line matching for backtrace
-- `-=` command (runs command, only shows output, does not show command)
+- Seperate parsing from running. This will help for easier linting of syntax etc.
+- Cache SHAs and output of each code block. If one sha changes, re-generate all code blocks, otherwise allow a re-render without code execution. Configure a check sum for busting the cache for instance a new version of Rails is released.
+
+
 - A way to run background processes indefinitely such as `rails server`
+  - Maybe a way to truncate them after only a period of time such as grab a few lines of `heroku local`.
+
+
+    ```
+    :::> background.start(command: "rails server")
+    ```
+
+    ```
+    :::>> background.read("rails server")
+    :::> | $ head -n 23
+    :::> background.clear
+    ```
+
+
+  - Breakpoints?
+- Better line matching for backtrace
+- `-=` command (runs command, only shows output, does not show command) ?
 - An easy test syntax?
 - Screenshot tool(s) ?!?!?!?!?!?! :)
-

data/bin/rundoc

@@ -28,19 +28,27 @@ class RundocCLI < Thor
   desc "build", "turns rundoc file into docs and a project"
   class_option  :path,   banner: "path/to/file.md",          optional: true, default: 'rundoc.md'
   def build
-    raise "#{@path} does not exist"   unless File.exist?(@path)
+    raise "#{@path} does not exist" unless File.exist?(@path)
+    raise "Expecting #{@path} to be a rundoc markdown file" unless File.file?(@path)
     source_contents = File.read(@path)
     tmp_dir         = @working_dir.join("tmp")
 
     FileUtils.remove_entry_secure(tmp_dir) if tmp_dir.exist?
     tmp_dir.mkdir
+    banner = <<~HEREDOC
+      <!-- STOP
+        This file was generated by a rundoc script, do not modify it.
+
+        Instead modify the rundoc script and re-run it.
+
+        Command: #{ $0 } #{$*.join(' ')}
+      STOP -->
+    HEREDOC
 
     puts "== Running your docs"
     Dir.chdir(tmp_dir) do
       @output = Rundoc::Parser.new(source_contents, Rundoc.parser_options).to_md
       Rundoc.sanitize(@output)
-      banner = "<!-- STOP\nThis file was generated by a rundoc script, don't modify it. \n"
-      banner << "Instead modify the rundoc script and re-run it.\nSTOP -->"
       @output = "#{banner}\n#{@output}"
     end
 
@@ -65,8 +73,8 @@ class RundocCLI < Thor
 
     FileUtils.remove_entry_secure(tmp_dir) if tmp_dir.exist?
 
-    puts "== Done, writing original source to #{project_dir}/source.md"
     source_path = project_dir.join("README.md")
+    puts "== Done, writing original source to #{source_path}"
     File.open(source_path, "w") { |f| f.write @output }
 
     puts "== Copying source"

data/lib/rundoc/code_command/file_command/append.rb

@@ -1,18 +1,23 @@
 class Rundoc::CodeCommand::FileCommand
   class Append < Rundoc::CodeCommand
+    include FileUtil
 
     def initialize(filename)
       @filename, line = filename.split('#')
-      @line_number    = Integer(line) if line
+      if line
+        @line_number = Integer(line)
+      else
+        @line_number = nil
+      end
     end
 
     def to_md(env)
       raise "must call write in its own code section" unless env[:commands].empty?
       before = env[:before]
       if @line_number
-        env[:before] = "In file `#{@filename}`, on line #{@line_number} add:\n\n#{before}"
+        env[:before] = "In file `#{filename}`, on line #{@line_number} add:\n\n#{before}"
       else
-        env[:before] = "At the end of `#{@filename}` add:\n\n#{before}"
+        env[:before] = "At the end of `#{filename}` add:\n\n#{before}"
       end
       nil
     end
@@ -36,7 +41,7 @@ class Rundoc::CodeCommand::FileCommand
 
     def insert_contents_into_at_line(doc)
       lines = doc.lines
-      raise "Expected #{@filename} to have at least #{@line_number} but only has #{lines.count}" if lines.count < @line_number
+      raise "Expected #{filename} to have at least #{@line_number} but only has #{lines.count}" if lines.count < @line_number
       result = []
       lines.each_with_index do |line, index|
         line_number = index.next
@@ -50,19 +55,17 @@ class Rundoc::CodeCommand::FileCommand
     end
 
     def call(env = {})
-      dir = File.expand_path("../", @filename)
-      FileUtils.mkdir_p(dir)
-
-      doc = File.read(@filename)
+      mkdir_p
+      doc = File.read(filename)
       if @line_number
-        puts "Writing to: '#{@filename}' line #{@line_number} with: #{contents.inspect}"
+        puts "Writing to: '#{filename}' line #{@line_number} with: #{contents.inspect}"
         doc = insert_contents_into_at_line(doc)
       else
-        puts "Appending to file: '#{@filename}' with: #{contents.inspect}"
+        puts "Appending to file: '#{filename}' with: #{contents.inspect}"
         doc = concat_with_newline(doc, contents)
       end
 
-      File.open(@filename, "w") do |f|
+      File.open(filename, "w") do |f|
         f.write(doc)
       end
       contents

data/lib/rundoc/code_command/file_command/remove.rb

@@ -1,5 +1,6 @@
 class Rundoc::CodeCommand::FileCommand
   class Remove < Rundoc::CodeCommand
+    include FileUtil
 
     def initialize(filename)
       @filename = filename
@@ -8,19 +9,19 @@ class Rundoc::CodeCommand::FileCommand
     def to_md(env)
       raise "must call write in its own code section" unless env[:commands].empty?
       before = env[:before]
-      env[:before] = "In file `#{@filename}` remove:\n\n#{before}"
+      env[:before] = "In file `#{filename}` remove:\n\n#{before}"
       nil
     end
 
     def call(env = {})
-      puts "Deleting '#{contents.strip}' from #{@filename}"
-      raise "#{@filename} does not exist" unless File.exist?(@filename)
+      puts "Deleting '#{contents.strip}' from #{filename}"
+      raise "#{filename} does not exist" unless File.exist?(filename)
 
       regex = /^\s*#{Regexp.quote(contents)}/
-      doc   = File.read(@filename)
+      doc   = File.read(filename)
       doc.sub!(regex, '')
 
-      File.open(@filename, "w") do |f|
+      File.open(filename, "w") do |f|
         f.write(doc)
       end
       contents

data/lib/rundoc/code_command/rundoc_command.rb

@@ -19,4 +19,4 @@ module ::Rundoc
 end
 
 
-Rundoc.register_code_command(:rundoc, ::Rundoc::CodeCommand::RundocCommand)
+Rundoc.register_code_command(:rundoc, RundocCommand)

data/lib/rundoc/code_command/write.rb

@@ -1,6 +1,23 @@
 module Rundoc
   class CodeCommand
+    module FileUtil
+      def filename
+        files = Dir.glob(@filename)
+        if files.length > 1
+          raise "Filename glob #{@filename.inspect} matched more than one file. Be more specific to only match one file. Matches:\n" + files.join("  \n")
+        end
+        files.first || @filename
+      end
+
+      def mkdir_p
+        dir = File.expand_path("../", filename)
+        FileUtils.mkdir_p(dir)
+      end
+    end
+
     class Write < Rundoc::CodeCommand
+      include FileUtil
+
       def initialize(filename)
         @filename = filename
       end
@@ -8,16 +25,14 @@ module Rundoc
       def to_md(env)
         raise "must call write in its own code section" unless env[:commands].empty?
         before = env[:before]
-        env[:before] = "In file `#{@filename}` write:\n\n#{before}"
+        env[:before] = "In file `#{filename}` write:\n\n#{before}"
         nil
       end
 
       def call(env = {})
-        puts "Writing to: '#{@filename}'"
-
-        dir = File.expand_path("../", @filename)
-        FileUtils.mkdir_p(dir)
-        File.open(@filename, "w") do |f|
+        puts "Writing to: '#{filename}'"
+        mkdir_p
+        File.open(filename, "w") do |f|
           f.write(contents)
         end
         contents
@@ -31,4 +46,4 @@ Rundoc.register_code_command(:write,        Rundoc::CodeCommand::Write)
 Rundoc.register_code_command(:'file.write', Rundoc::CodeCommand::Write)
 
 require 'rundoc/code_command/file_command/append'
-require 'rundoc/code_command/file_command/remove'
+require 'rundoc/code_command/file_command/remove'

data/lib/rundoc/code_command.rb

@@ -1,12 +1,16 @@
 module Rundoc
   class CodeCommand
-    attr_accessor :hidden, :render_result, :command, :contents, :keyword
-    alias :hidden? :hidden
+    attr_accessor :render_result, :render_command, :command, :contents, :keyword
     alias :render_result? :render_result
+    alias :render_command? :render_command
 
     def initialize(arg)
     end
 
+    def hidden?
+      !render_command? && !render_result?
+    end
+
     def not_hidden?
       !hidden?
     end

data/lib/rundoc/code_section.rb

@@ -40,7 +40,7 @@ module Rundoc
 
     def render
       result = []
-      env = {}
+      env    = {}
       env[:commands] = []
       env[:before]   = "#{fence}#{lang}"
       env[:after]    = "#{fence}"
@@ -57,11 +57,12 @@ module Rundoc
 
         env[:commands] << { object: code_command, output: code_output, command: code_line}
 
-        if code_command.render_result?
-          result << [code_line, code_output]
-        else
-          result << code_line unless code_command.hidden?
-        end
+        tmp_result = []
+        tmp_result << code_line   if code_command.render_command?
+        tmp_result << code_output if code_command.render_result?
+
+        result << tmp_result unless code_command.hidden?
+        result
       end
 
       return "" if hidden?
@@ -112,16 +113,34 @@ module Rundoc
       command      = match[:command]
       tag          = match[:tag]
       statement    = match[:statement]
-
       code_command = Rundoc.code_command_from_keyword(command, statement)
 
       case tag
-      when /\-/
-        code_command.hidden        = true
+      when /\A>>/ # show command, show result
+        code_command.render_command = true
+        code_command.render_result  = true
+      when /(\A>\-)|(\A>[^\-]?)/ # show command, not result
+        code_command.render_command = true
+        code_command.render_result  = false
+      when /\A\->/ # hide command, show result
+        code_command.render_command = false
+        code_command.render_result  = true
+      when /(\A\-)|(\A\-\-)/ # hide command, hide result
+        code_command.render_command = false
+        code_command.render_result  = false
+      # ========= DEPRECATED ==========
       when /\=/
-        code_command.render_result = true
+        puts "Deprecated: `:::=` is deprecated use `:::>>` instead"
+        puts "  :::>> #{command} #{statement}"
+        code_command.render_command = true
+        code_command.render_result  = true
       when /\s/
-        # default do nothing
+        puts "Deprecated: `:::` is deprecated use `:::>` instead"
+        puts "  :::> #{command} #{statement}"
+        code_command.render_command = true
+        code_command.render_result  = false
+      else
+        raise "Tag is invalid #{tag.inspect}"
       end
 
       @stack   << "\n" if commands.last.is_a?(Rundoc::CodeCommand)

data/lib/rundoc/parser.rb

@@ -5,7 +5,7 @@ module Rundoc
     GITHUB_BLOCK       = '^(?<fence>(?<fence_char>~|`){3,})\s*?(?<lang>\w+)?\s*?\n(?<contents>.*?)^\g<fence>\g<fence_char>*\s*?\n'
     CODEBLOCK_REGEX    = /(#{GITHUB_BLOCK})/m
     COMMAND_REGEX      = ->(keyword) {
-                             /^#{keyword}(?<tag>(\s|=|-)?)\s*(?<command>(\S)+)\s+(?<statement>.*)$/
+                             /^#{keyword}(?<tag>(\s|=|-|>)?(=|-|>)?)\s*(?<command>(\S)+)\s+(?<statement>.*)$/
                             }
 
     attr_reader :contents, :keyword, :stack

data/lib/rundoc/version.rb

@@ -1,3 +1,3 @@
 module Rundoc
-  VERSION = "0.0.1"
-end
+  VERSION = "0.0.2"
+end

data/rundoc.gemspec

@@ -8,8 +8,8 @@ Gem::Specification.new do |gem|
   gem.version       = Rundoc::VERSION
   gem.authors       = ["Richard Schneeman"]
   gem.email         = ["richard.schneeman+rubygems@gmail.com"]
-  gem.description   = %q{rundoc turns docs to runable code}
-  gem.summary       = %q{rundoc generates runable code from docs}
+  gem.description   = %q{runDOC turns docs to runable code}
+  gem.summary       = %q{runDOC generates runable code from docs}
   gem.homepage      = "https://github.com/schneems/rundoc"
   gem.license       = "MIT"
 
@@ -18,11 +18,11 @@ Gem::Specification.new do |gem|
   gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
   gem.require_paths = ["lib"]
 
-
   gem.add_dependency "thor"
   gem.add_dependency "repl_runner"
 
   gem.add_development_dependency "rake"
   gem.add_development_dependency "mocha"
+  gem.add_development_dependency "test-unit"
 end