manpage rendering issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- cli, documentation
Research direction
Start by running ./target/debug/uudoc manpage for chown and echo, then inspect the manpage-generation path responsible for SYNOPSIS, OPTIONS, and EXTRA output. Compare the generated groff with the issue examples across the listed commands; done means positional parameters, option spacing, and list formatting render correctly.
Written by the indexing model from the issue text.
Description
450e7cfee996d26ccf516e5bd11f9bd673a5b3c6
SYNOPSIS
[file]can be multiple, i.e.[file...]- b2sum
- cat
- chmod
- cksum, etc
- positional parameters are missed, e.g.
[file...]- chown, etc
- space after short only options, e.g.
[-e ]in cat- cat
- chmod
- chown, etc
./target/debug/uudoc manpage chown:
.SH SYNOPSIS
\fBchown\fR [\fB\-\-help\fR] [\fB\-c\fR|\fB\-\-changes\fR] [\fB\-\-from\fR] [\fB\-\-preserve\-root\fR] [\fB\-\-no\-preserve\-root\fR] [\fB\-\-quiet\fR] [\fB\-R\fR|\fB\-\-recursive\fR] [\fB\-\-reference\fR] [\fB\-f\fR|\fB\-\-silent\fR] [\fB\-v\fR|\fB\-\-verbose\fR] [\fB\-H \fR] [\fB\-L \fR] [\fB\-P \fR] [\fB\-\-dereference\fR] [\fB\-h\fR|\fB\-\-no\-dereference\fR] [\fB\-V\fR|\fB\-\-version\fR]
OPTIONS
- stray positional parameters, e.g.
[file]in- b2sum
- base32
- base64
- chmod, etc
EXTRA
- list is malformed
- cksum
- dd
- echo, etc
./target/debug/uudoc manpage echo:
.SH EXTRA
Echo the STRING(s) to standard output.
If \-e is in effect, the following sequences are recognized:
\- \\ backslash
\- \\a alert (BEL)
\- \\b backspace
\- \\c produce no further output
\- \\e escape
\- \\f form feed
\- \\n new line
\- \\r carriage return
\- \\t horizontal tab
\- \\v vertical tab
\- \\0NNN byte with octal value NNN (1 to 3 digits)
\- \\xHH byte with hexadecimal value HH (1 to 2 digits)
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
U - ls
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
U - ls
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
U - tr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
U - date
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
U - date
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in uutils/coreutils
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100