hxbrief: Nested operation should still apply any "non-transient" behaviour
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The hxbrief behaviour can be split into two aspects
- What is printed to the console while the child process is running
- What ends up as hxbrief's stdout/stderr output once the child process has finished
The former we do not want in the case of nested operation, but the latter does make sense. Setting --lines 0 is a good first approach, but not sufficient, because a) we still would have a status line b) strictly speaking we may be delaying certain output more than strictly necessary, arguably buggy behaviour c) for some reason there is some other bug as well that leads some additional output.
Not sure if the whole thing is worth implementing. But let's keep it just to document the current behaviour and the problems one might run into.
Contributor guide
No contributing guide indexed for this repository
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 at the hxbrief entry point and trace how nested operation handles --lines 0, the status line, and child-process output. Done means nested runs suppress transient console output while preserving the intended final stdout/stderr behavior without unnecessary delay or extra output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100