Help messages too many blank rows

[wormtql]

I write an application with two sub commands, and the help message of one subcommand looks like this:

Honkai: Star Rail item scanner

Usage: yas.exe starrail [OPTIONS]

Options:
      --min-star <MIN_STAR>
          最小星级 [default: 4]
      --min-level <MIN_LEVEL>
          最小等级 [default: 0]
      --ignore-dup
          忽略重复物品
      --verbose
          显示详细信息
      --number <NUMBER>
          指定遗器数量 [default: -1]
      --max-row <max-row>
          最大扫描行数 [default: -1]
      --scroll-delay <scroll-delay>
          翻页时滚轮停顿时间（ms）（翻页不正确可以考虑加大该选项） [default: 80]
      --max-wait-switch-item <max-wait-switch-item>
          切换物品最大等待时间（ms） [default: 800]
      --cloud-wait-switch-item <cloud-wait-switch-item>
          云游戏切换物品等待时间（ms） [default: 300]
  -f, --format <format>
          输出格式 [default: hsr] [possible values: march7th, hsr]
  -o, --output-dir <output-dir>
          输出目录 [default: .]
  -h, --help
          Print help
  -V, --version
          Print version

But the other help message includes too many unnessary blank lines:

Genshin Impact item scanner

Usage: yas.exe genshin [OPTIONS]

Options:
  -f, --format <format>
          输出格式

          [default: mona]

          Possible values:
          - mona
          - mingyu-lab
          - good
          - csv
          - all:        Export all formats

  -o, --output-dir <output-dir>
          输出目录

          [default: .]

      --min-star <MIN_STAR>
          最小星级

          [default: 4]

      --min-level <MIN_LEVEL>
          最小等级

          [default: 0]

      --ignore-dup
          忽略重复物品

      --verbose
          显示详细信息

      --number <NUMBER>
          指定圣遗物数量

          [default: -1]

Is there any switch on how to control this behavior

[epage]

The second is called "long helpand should only show up for--helpbut not-h`.

"long help" gets activated when you provide long_about, long_help, etc. These are implicitly provided in the derive API when using multi-paragraph doc comments. I'd have to double check but I think ValueEnum may be an exception and having a PossibleValue::help / doc-comment is considered an indicator of wanting "long" help. If using the derive API and its the possible value doc comment, you can disable it with #[value(help = None)] on the all variant.