Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Plain `termlens diff` output ends with a blank line, and says "1 rows unchanged"

Open Beginner friendly
#652 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli, testing

Research direction

Read termlens-cli/src/main.rs around line 409 and diff.rs around lines 312–315, then find the CLI output tests. Verify the plain diff's output bytes end in exactly one newline and that a count of one uses singular wording; add the required CHANGELOG entry. Done when the tests pass and the changelog records the CLI output change.

Written by the indexing model from the issue text.

Description

bug good first issue

What happens.

$ termlens diff --color never w1.snap w2.snap | cat -A | tail -2
… 1 rows unchanged$
$

There is an extra empty line after the diff, and the count is "1 rows". The extra line also shows up as a stray blank line before the closing fence in the report action's summary. "no difference" and the coloured output end without it.

Cause. termlens-cli/src/main.rs:409 prints a newline after ScreenDiff's Display, which already ends with writeln! (screen/diff.rs:312-315). The count's wording is at diff.rs:312.

Fix. Drop the extra newline, and use "row" for a count of one.

Done when the plain output ends with exactly one newline, with a test that checks the bytes. Note that this changes the CLI's output; record it in the CHANGELOG.

Dominant language
Rust
Stars
28
Forks
24
Avg merge
11h 23m
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vyncint/termlens

All issues in vyncint/termlens

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.