Visual bugs in cmd with stray underlines

[thatbakamono]

Please complete the following tasks

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

Rust Version

rustc 1.65.0-nightly (f03ce3096 2022-08-08)

Clap Version

4.0.18

Minimal reproducible code

use clap::Command;

fn main() {
    Command::new("repro").get_matches();
}

Steps to reproduce the bug with the above code

cargo run -- --help

Actual Behaviour

Expected Behaviour

Additional Context

The first screenshot shows cmd, the second screenshot shows windows terminal. I wasn't able to trigger this bug in windows terminal but it's worth noting that even in cmd, it doesn't always happen:

Debug Output

No response

[epage]

Tbat most likely means something is going wrong with termcolor's wincon support as that is most likely the main difference between the two terminals. Whats especially weird is that there is no reason to put an underline after "information" as we only use underline in headers and so we aren't touching it at that point.

If you want to go an extra step, reproducing this in termcolor and creating an upstream issue would be great. With #1433, we will most likely be moving off of termcolor though, so we'll need to keep in mind to fix this when we do.

[saffaffi]

I'm seeing this happen in Wezterm, but specifically only when the help text is printed when the output in the terminal window has reached the bottom. It happens under that condition with both TERM=wezterm and TERM=xterm-256color.

[YamatoSecurity]

We also have the same problem when running on Windows 10 Command Prompt or Powershell Prompt.
(It does not have this bug in Windows 11)
Rust: 1.67.1
Clap: 4.1.6

At first it looks like this:

If I resize the window, the line will extend out from the Options group name: