anchor.diff:      }
   }
   ```
  -
  -=== Case Sensitivity
  -By default, all options and subcommands are case sensitive.
  -Case sensitivity can be switched off globally, as well as on a per-command basis.
  -
  -To toggle case sensitivity for all commands, use the `CommandLine::setSubcommandsCaseInsensitive` and `CommandLine::setOptionsCaseInsensitive` methods.
  -Use the `CommandSpec::subcommandsCaseInsensitive` and `CommandSpec::optionsCaseInsensitive` methods to give some commands a different case sensitivity than others.
  -
  -Where possible, picocli will try to prevent ambiguity: when multiple options with the same name are registered in a command, a `DuplicateOptionAnnotationsException` is thrown.
  -When multiple subcommands with the same name are registered in a command, a `DuplicateNameException` is thrown.
  -
  -With case sensitivity switched off, the same principle applies: multiple options whose names differ only in case cannot be registered in a command.
  -Similarly, multiple subcommands cannot be registered when their names differ only in case.
  -
  -[WARNING]
  -====
  -When a combination of POSIX options resembles a long option, picocli will prioritize the long option.
  -This is the case regardless of case sensitivity, but be aware that with case sensitivity switched off, the chance of such collisions increases.
  -For example, if a command has POSIX options `-a`, `-b`, and `-c`, and a long option `-ABC`, then, when the user specifies `-abc`, picocli will recognize it as the long option `-ABC`, not as the POSIX options.
  -====
  -
  -See the https://github.com/remkop/picocli/tree/master/picocli-examples/src/main/java/picocli/examples/casesensitivity[casesensitivity] package in `picocli-examples` for some examples.
  -
   
   == Help
   
  
positive.code: === Options
  An option must have one or more `names`.
  Picocli lets you use any option name you want.
  
  TIP: You may be interested in this http://catb.org/~esr/writings/taoup/html/ch10s05.html#id2948149[list of common option names]. Following these conventions may make your application more intuitive to use for experienced users.
  
  
negative.code: 
  == Parser Configuration
  
  === Case Sensitivity
  By default, all options and subcommands are case sensitive.
  Case sensitivity can be switched off globally, as well as on a per-command basis.
  
  To toggle case sensitivity for all commands, use the `CommandLine::setSubcommandsCaseInsensitive` and `CommandLine::setOptionsCaseInsensitive` methods.
  Use the `CommandSpec::subcommandsCaseInsensitive` and `CommandSpec::optionsCaseInsensitive` methods to give some commands a different case sensitivity than others.
  
  Where possible, picocli will try to prevent ambiguity: when multiple options with the same name are registered in a command, a `DuplicateOptionAnnotationsException` is thrown.
  When multiple subcommands with the same name are registered in a command, a `DuplicateNameException` is thrown.
  
  With case sensitivity switched off, the same principle applies: multiple options whose names differ only in case cannot be registered in a command.
  Similarly, multiple subcommands cannot be registered when their names differ only in case.
  
  [WARNING]
  ====
  When a combination of POSIX options resembles a long option, picocli will prioritize the long option.
  This is the case regardless of case sensitivity, but be aware that with case sensitivity switched off, the chance of such collisions increases.
  For example, if a command has POSIX options `-a`, `-b`, and `-c`, and a long option `-ABC`, then, when the user specifies `-abc`, picocli will recognize it as the long option `-ABC`, not as the POSIX options.
  ====
  
  See the https://github.com/remkop/picocli/tree/master/picocli-examples/src/main/java/picocli/examples/casesensitivity[casesensitivity] package in `picocli-examples` for some examples.
  
  === Overwriting Single Options
  
  When a single-value option is specified multiple times on the command line, the default parser behaviour is
  