QuantStack / QuantStack/git2cpp
Handle `cerr` in terminal pager
還沒有人認領這個 Issue。
- 主要語言
- C++
- 星號
- 6
- 分支
- 5
- 平均合併
- 4 小時 22 分鐘
- 30 天內合併 PR
- 4
描述
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?
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
此 issue 未指出檔案、測試或特定的進入點。先找到 terminal pager 的實作並閱讀 #46 的討論,接著確定專案接受哪種處理 cerr 的策略。完成的標準是依照該決定處理 cerr,且不阻礙 pager 工作。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- cpp
- 領域
- cli
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100