anchor.diff:  ----
     // regular
     {REFSTART} / [^>\n]+ {REFEND} { yybegin(REF); return AsciiDocTokenTypes.REFSTART; }
  -  // autocomplete
  +  // auto-complete
     {REFSTART} / [^>\n ]* {AUTOCOMPLETE} { yybegin(REFAUTO); return AsciiDocTokenTypes.REFSTART; }
   ----
   --
  
positive.code: Once you add a new token you will need to add it to `AsciiDocColorSettingsPage` so users can customize the colors of their theme.
  This class references also `SampleDocument.adoc` and `AsciiDocBundle.properties`, therefore you'll probably need to change these two files as well.
  
  === Parsing
  
  TODO: parsing, refactoring, folding, linking, autocompletion, finding references
  
  == Preview rendering
  
  
negative.code: To work around this issue blocks are parsed first in state `MULTILINE`, then in state `SINGLELINE`, and finally `INSIDE_LINE` to implement a hierarchy and some ordering of matches.
  --
  
  auto-completion::
  +
  --
  Expressions described above match expressions once they have their closing syntax completed and it is essential for the correct highlighting.
  To support autocomplete the matching must handle an expression where only the left part of the expression exists.
  
  A special case is in the parser to support autocompletion, as IntelliJ inserts a special string when parsing the content for autocompletion (named `auto-complete` in our parser).
  
  In the case for references (`\<<ref>>`) there are two rules, one for regular parsing and highlighting, one without:
  
  