pr: --first-line-number counts lines on skipped pages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
Research direction
Start in src/uu/pr/src/pr.rs: the issue points to the option parser at lines 796–802 and pagination loop at lines 1268–1285. Compare how omitted -N and explicit -N1 are represented, then trace when the line number advances relative to the printed page. Add regression coverage for the shown -N cases; done when the output matches the GNU results in the table.
Written by the indexing model from the issue text.
Description
With one line per page, +2 skips the first line. The help for -N says numbering starts at the first line of the first page printed, so the line containing b should be numbered 8.
printf 'a\nb\n' | LC_ALL=C pr -t -l1 +2 -n:1 -N8
On Linux, uutils 108f21e prints 9:b. GNU coreutils 9.12 prints 8:b. Both exit 0.
There is also a distinction worth covering in a regression test:
| Last argument | GNU 9.12 | uutils 108f21e |
|---|---|---|
Omit -N |
2:b |
2:b |
-N1 |
1:b |
2:b |
-N8 |
8:b |
9:b |
The option parser stores the same starting number for an omitted -N and an explicit -N1. The pagination loop increments the line number before checking whether the page will be printed.
- Dominant language
- Rust
- Stars
- 24.4k
- Forks
- 2.2k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 434
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 - shred
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
chown -v: `+ID` spec echoed verbatim on a broken symlinkPossibly taken @sunsss123soldier claimed this 1 day ago. Opengood first issue oss-scanner U - chown
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
dircolors: --csh doesn't escape `!`Possibly taken @majidninja claimed this 2 days ago. Opengood first issue oss-scanner U - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uutils/coreutils#16496 · 1 comment ·
Maintainers usually reply within 1 day
-
dircolors: directory operand exits 2 with a custom message, GNU prints 'read error: Is a directory' and exits 1Possibly taken @emirmrkaljevic claimed this 3 days ago. OpenU - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
test_hostid.rs lacks test cases with frozen ip addr e.g. unshare -ru sh -c "hostname 127.0.0.1 && hostid"Possibly taken @costajohnt claimed this 3 days ago. OpenU - hostid
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ClickHouse/ClickHouse#132519 ·
Maintainers usually reply within 1 day
-
Pattern-clip compiler tests miss the clip cap, sort order, muted output and count/emit agreementOpenarea: engine type: test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
YuriiMurha/grooviq#224 ·
Maintainers usually reply within 1 day
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
zed-industries/zed#67109 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#15500 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day