You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As explored in #40, the intermingling of Apt progress reporting and the messages coming from batch files extracted from packages can make it difficult to determine where a problem is coming from. It would be good to portray these messages and errors in way that makes it easier to differentiate.
One idea is to redirect batch stdout stderr to another console or log file(s). The more I think about this though the less attracted I am. Who wants to wade through possibly dozens or hundreds of logfiles in the event of an issue? Maybe could just draw them in different colours?
Anyway, no solution or plan for one at this point, just a ticket to attach one to later.
The text was updated successfully, but these errors were encountered:
As explored in #40, the intermingling of Apt progress reporting and the messages coming from batch files extracted from packages can make it difficult to determine where a problem is coming from. It would be good to portray these messages and errors in way that makes it easier to differentiate.
One idea is to redirect batch stdout stderr to another console or log file(s). The more I think about this though the less attracted I am. Who wants to wade through possibly dozens or hundreds of logfiles in the event of an issue? Maybe could just draw them in different colours?
Anyway, no solution or plan for one at this point, just a ticket to attach one to later.
The text was updated successfully, but these errors were encountered: