anchor.diff:  ----
   
   CAUTION: Markup styles cannot be nested, for example: `@|bold this @|underline that|@|@` will not work. You can achieve the same by combining styles, for example: `@|bold this|@ @|bold,underline that|@` will work fine.
  +
   === More Colors
   Most terminals support a https://en.wikipedia.org/wiki/ANSI_escape_code#Colors[256 color indexed palette]:
   ----
  
positive.code: image:ExampleUsageANSI.png[Screenshot of usage help with Ansi codes enabled]
  
  == How to use it
  The easiest is to create a class and annotate its fields or methods with `@Option` or `@Parameters` to declare what options and positional parameters your application expects.
  While parsing the command line, picocli will initialize these fields based on the command line arguments.
  If your class implements `Runnable` or `Callable`, you can let picocli kick off your application after parsing is successfully completed.
  
  NOTE: For applications that cannot use the annotations, there is also a programmatic API for defining what options and positional parameters to expect, and a programmatic API for handling parse results. The programmatic API is not covered in this Quick Guide.
  
  === Example
  Here is a small example application that uses the `CommandLine.call` <<Less Boilerplate,convenience method>>
  
negative.code: Options have a name, positional parameters are usually the values that follow the options,
  but they may be mixed.
  
  image:OptionsAndParameters2.png[Example command with annotated @Option and @Parameters]
  
  Picocli has separate annotations for options and positional parameters.
  
  