Thomas Otto

Not reproducible for me, neither with debug nor release (nor full re-)builds using Rust 1.64.0. Maybe it is part of your `~/.gitconfig` or the repo config? Running it with `HOME=/...

I see, raw ansi codes produced by `colorMovedWS` or `colorMoved` cause this, as the tabstop-aware expansion of raw lines (which are just `&str` by then) also counts the ultimately invisible...

Variable tab expansion is quite tricky, and I have to ask: Is this worth it? Most tabs in code will be leading ones which work fine with the fixed expansion...

So, if this error shows up in the side-by-side view it can get truncated, all I can do is trim the message a bit. Well, still better than crashing... Remind...

Now that `--help` is handled manually, piping the output into `less -R` is easy. And clap doesn't seen to support a pager currently.

The fmt is fixed, but sending the output into a pager via `OutputType::from_mode` (now using a lighter `PagerCfg`) doesn't work, the default pager `less` just quits after the first page....

Now with pager support, even listens to `PAGER` etc. env vars for configuration (but not `--paging never`). The `full---help-output.md` markdown is a bit out of sync, but could be generated...

The full help output has to be regenerated (some ansi2md util would help), and I have to check that the big moved textblock in `cli.rs` is still correct.

Also fixed the rust 1.80 build, note the Cargo.* changes. FTR, the build for the time crate was: ``` --> /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.31/src/format_description/parse/mod.rs:83:9 | 83 | let items = format_items | ^^^^^...

When suggesting to someone to use `rg` instead of "legacy" `grep -R .. | grep -v -e .git -e build` or `git grep ..` on the _very first try_ (maybe...