René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Handle `cerr` in terminal pager","articleBody":"Need to handle `cerr` as well as `cout` in terminal pager. Discussion from #46:\n\nIan:\nWe do need a strategy for what to do with cerr, but I don't know what is best yet.\n\nCurrently 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:\n\n1. 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.\n2. 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.\n3. 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.\n\nJohan:\nI 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?","author":{"url":"https://github.com/ianthomas23","@type":"Person","name":"ianthomas23"},"datePublished":"2025-10-21T07:38:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/49/git2cpp/issues/49"}