Handle `cerr` in terminal pager
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue does not identify files, tests, or a specific entry point. Start by locating the terminal pager implementation and reading the discussion from #46, then establish which strategy for handling cerr the project accepts. Done means cerr is handled according to that decision without blocking the pager work.
Written by the indexing model from the issue text.
Description
Need to handle cerr as well as cout in terminal pager. Discussion from #46:
Ian:
We do need a strategy for what to do with cerr, but I don't know what is best yet.
Currently cerr will be written to the normal terminal buffer, so it won't be seen whilst the alternative buffer is being used but it reappears when the alternative buffer is disabled. This is perhaps not a good solution, but I don't think it is too bad for a first implementation. Some other options:
- Capture it and sent it to the same place as cout, it will appear in the output flow in the alternative buffer. We'd probably need to colour it to make is easily visible as it could be anywhere.
- Capture it and display it at the bottom of the alternative buffer for better visibility, but then there might be quite a lot of information displayed.
- Capture it and if anything at all is written to it we could avoid using the pager at all, just display the errors in the normal terminal flow.
Johan:
I have a preference for option 1, but I think we can discuss it in a dedicated issue and solve it in a dedicated PR so that it does not block this one, WDYT?
- 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
- 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.
More from QuantStack/git2cpp
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
QuantStack/git2cpp#134 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
QuantStack/git2cpp#131 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
QuantStack/git2cpp#62 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
QuantStack/git2cpp#51 · 1 comment ·
All issues in QuantStack/git2cpp
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·