expand/unexpand: no output if input is read from stdin
Open
Nobody has claimed this yet.
U - expand
U - unexpand
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
When providing the input interactively via standard input, both GNU expand and GNU unexpand show the results whereas our versions don't.
$ expand -t3
a
a
^C
$ cargo run -q expand -t3
a
^C
$ unexpand -t3
a b
a b
^C
$ cargo run -q unexpand -t3
a b
^C
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.
Research direction
Start by reproducing the reported behavior with the expand and unexpand command entry points, piping or entering input through standard input. Compare both commands with GNU expand and unexpand; done means each local command emits transformed output interactively before stdin closes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100