Paragraphs for long help derived from doc comments may be splitted on more cases

[JohanVonElectrum]

Please complete the following tasks

• I have searched the discussions
• I have searched the open and rejected issues

Rust Version

rustc 1.80.0 (051478957 2024-07-21)

Clap Version

4.5.20

Minimal reproducible code

use clap::Parser;

#[derive(Debug, Parser)]
struct GlobalArgs {
    /// Verbose level
    ///
    /// Levels:  
    /// - 0: info + warn + error  
    /// - 1: debug + info + warn + error  
    /// - 2: trace + debug + info + warn + error
    #[arg(short, long, action = clap::ArgAction::Count)]
    verbose: u8,
}

#[derive(Debug, Parser)]
#[command(version, about, long_about = None)]
struct Args {
    #[clap(flatten)]
    global: GlobalArgs,
}

fn main() {
    let args = Args::parse();
    println!("{:?}", args);
}

Steps to reproduce the bug with the above code

cargo run -- --help

Actual Behaviour

Options:
-v, --verbose...
Verbose mode, print more information

      Levels: - 0: info + warn + error - 1: debug + info + warn + error - 2: trace + debug + info + warn + error

Expected Behaviour

Options:
-v, --verbose...
Verbose mode, print more information

      Levels:
      - 0: info + warn + error
      - 1: debug + info + warn + error
      - 2: trace + debug + info + warn + error

Additional Context

I expect a paragraph to split on lines ending on double space or backslash or when starting by - or <num>. . Note that in the provided minimal example the lines from Level: to - 1: ... end with double space.

Debug Output

No response

[epage]

This appears to be a duplicate of #2389, closing in favor of that

[JohanVonElectrum]

Thank you for pointing that out. I had searched for issues related to newlines but didn’t find #2389, as it addresses general markdown parsing. I now see the overlap and will contribute to the discussion there. Thanks for the guidance!

[epage]

Fully understand the difficulty of finding issues and identifying whats relevant!