QuantStack / QuantStack/git2cpp
Improve terminal pager performance
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6
- Forks
- 5
- Avg merge
- 4h 22m
- Merged PRs (30d)
- 4
Description
The terminal pager is quite simple, it waits for the git2cpp command to produce all of its output before it is displayed. This can be slow for e.g. a git2cpp log of a big repo. Commands in a real terminal would run the pager in a separate process and pipe the output from the command to it, so it fills progressively. We cannot run the pager as a separate process in cockle so we'll need to find some other way of doing this better.
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 by locating the terminal pager and the entry point that runs git2cpp commands and collects their output. Investigate how output buffering currently delays display and identify an approach compatible with cockle without a separate pager process; done means large commands such as git2cpp log display progressively.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100