-
Notifications
You must be signed in to change notification settings - Fork 494
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
Improve verbose + serialize-output usage #660
Improve verbose + serialize-output usage #660
Conversation
yeah I kinda like that ... before it was not really obvious what output belonged together ... |
can you |
Unfortunately github is having a bad day, so no CI for now. Once it's back up, I'll retrigger CI 👍. |
With this combination of flags, all commands will be printed first, and then all outputs. I think it's much more useful to print each command followed by its output in sequence.
I think this is because `sort_by` in ruby is not stable, so ties are not resolved consistenly across versions.
@grosser There were only two failures on Windows, and I think it's because Let me know if I should extract those changes to a separate PR, I just wanted to see if I could get the build fully green :) |
Thanks so much @grosser for merging and releasing and for your work in general! |
np, thx for the cleanup PR ... and finally some green tests :)
…On Wed, Oct 24, 2018 at 11:35 AM David Rodríguez ***@***.***> wrote:
Thanks so much @grosser <https://github.com/grosser> for merging and
releasing and for your work in general!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#660 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAsZ-BxIVldpj_0NS1ugG5M1eeiYwKMks5uoLMCgaJpZM4XzRai>
.
|
With this combination of flags, all commands will be printed first, and then all outputs. I think it's more useful to print each command followed by its output in sequence.
Before
After