-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep git output #10206
Comments
Related to #7244 |
Duplicate of #7244 |
@RussKie @gerhardol Thanks for taking a look. I agree the issue you referred to is relevant, i.e. implementing it would cover this issue, but not necessarily in the best way. I believe the focus of that request is largely on troubleshooting and thus mainly on persistence of the logs. Here, on the other hand, the focus is on normal operation, so I'd like to point out some specifics, in case you want to reconsider:
|
Occasionally, I close the progress dialog too quickly (my click finger is quicker than I think).
That would be the best compromise IMO. |
I would make sure some limit was set. Make this log a tail like command that does not crash the app because you left app running for days and the log has grown and eating working set of process. Why not do a tail watch on a temp file we write to with a wrapped write like echo "$(tail -1000 myscript.log)" > myscript.log Then you would have a persisted log of most recently ran commands in the log and would be useful for debugging issues. |
Feature description
Currently we have 2 options regarding the output printed by potentially long-running git commands, such as
fetch
,checkout
, etc.:There is a "Git command log" window, but it can't show the commands' output, as far as I can tell.
I think a middle ground would be good here: save the output for later and don't require the user to read and acknowledge it before proceeding. The log could be integrated into the existing "Git command log", but maybe it even deserves a tab of its own next to "Console" to make it easy to keep an eye on.
Environment
The text was updated successfully, but these errors were encountered: