anchor.diff:  All right, it ran!
   The output file, [path]_sample.html_, was created in the same directory as the source file, [path]_sample.adoc_.
   
  -The relevant bits of the input and output are show below.
  +The relevant bits of the input and output are shown below.
   
   ._lib/emoji-inline-macro/sample.adoc_
   ```asciidoc
  
positive.code: - *BlockMacroProcessor* - adds a custom block macro
  - *InlineMacroProcessor* - adds a custom inline macro
  
  The type of extension (e.g, `-block-macro`) is always used in the name of the extension load file and directory to make it easy to distinguish.
  You can also look for examples using `git grep`.
  For example, to look for a `BlockMacroProcessor`, run the following command:
  
    $ git grep BlockMacroProcessor lib/
  
  You will get a result like this:
  
  ....
  lib/chart-block-macro/extension.rb:class ChartBlockMacro < Extensions::BlockMacroProcessor
  
negative.code: 
  === Formal
  
  If you're creating a more complex extension or want to enable reuse, you're encouraged to move the extension code to the [path]_extension.rb_ inside a directory with the same base name as the registration file.
  In the case of a block, block macro or inline macro, this enables you to register the extension multiple times.
  
  ._lib/sample-block.rb_
  ```ruby
  