anchor.diff:  @Command(separator = " ")
   ----
   
  -NOTE: the `@Command(separator = " ")` annotation also affects how picocli parses the command line. If you want the command parser to recognize one separator (`=` for example), but display a different separator (a space for example) in the usage help message, you need to programmatically configure the parser with the `CommandLine.setSeparator` method. See <<option-parameter-separators>>.
  +NOTE: the `@Command(separator = " ")` annotation also affects how picocli parses the command line. If you want the command parser to recognize one separator (`=` for example), but display a different separator (a space for example) in the usage help message, you need to programmatically configure the parser with the `CommandLine.setSeparator` method. See <<Option-Parameter Separators>>.
   
   === Hidden Options and Parameters
   Options and Parameters with the `hidden` attribute set to `true` will not be shown in the usage help message.
  
positive.code:                 "along with a log message from the user describing the changes.")
  class GitCommit { ... }
  ----
  The usage help message generated from this class is shown below in <<expanded-example>>.
  
  === Unsorted Option List
  By default the options list displays options in alphabetical order. Use the `sortOptions = false` attribute to display options in the order they are declared in your class.
  
negative.code: ----
  
  The usage help message for each subcommand is produced by calling `CommandLine.usage(new SubCommand(), out)`.
  For example, see <<Section Headings>> for an example subcommand (`git-commit`), which produces the help message shown
  in <<Expanded Example>>.
  
  == Subclassing for Reuse
  Picocli will walk the class hierarchy to check for annotations, so you can declare common @Options and @Command attributes on a superclass and override these fields or attributes on a subclass.
  