You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an example, the jj next --help output contains two commit graphs. These are included literally in the jj-next.1 manual as generated by jj util install-manpages. This isn't proper roff markup:
For example, when the offset is 1:
.PP
```text
D D @
| |/
C @ => C
|/ |
B B
```
.PP
The result as displayed by a roff formatter (e.g., groff -man -Tascii jj-next.1 | less -R or man) squashes everything onto a single line and is therefore unreadable:
For example, when the offset is 1:
```text D D @ | |/ C @ => C |/ | B B ```
I haven't looked at what exactly is involved in generating the manpages, so this might not be a bug in jj itself but rather in one of the crates responsible for the conversion.
The text was updated successfully, but these errors were encountered:
I haven't actually looked into clap's man page generation. Also cc @bnjmnt4n , not sure if you did.
Re yuya's point, if you are referring to the same feature I'm thinking of, it is discussed in clap-rs/clap#5900 (comment). They have not brought up man pages at all, so I'm not sure if the feature is meant to help with that. If that feature is related to this problem, we should probably point it out in that thread.
As an example, the
jj next --help
output contains two commit graphs. These are included literally in thejj-next.1
manual as generated byjj util install-manpages
. This isn't proper roff markup:The result as displayed by a roff formatter (e.g.,
groff -man -Tascii jj-next.1 | less -R
orman
) squashes everything onto a single line and is therefore unreadable:I haven't looked at what exactly is involved in generating the manpages, so this might not be a bug in jj itself but rather in one of the crates responsible for the conversion.
The text was updated successfully, but these errors were encountered: