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

Improve terminal pager performance

Open
#131 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
cli, performance

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.

Description

enhancement

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.

Dominant language
C++
Stars
6
Forks
5
Avg merge
4h 22m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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 QuantStack/git2cpp

All issues in QuantStack/git2cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.