On Wed, 15 Mar 2023 at 18:02, Jeff King <peff@xxxxxxxx> wrote: > Now, none of that is _strictly_ necessary. We could just dump the same > human-readable progress to the progress command that we dump to stderr > now, and it could scrape it for things that look like progress, and pass > everything else through. But then, you can already do that with: > > git clone --progress ... 2>&1 | my-progress-scraper > > (and it looks like the asciinema you showed is probably just a > syntactically nicer version of that with support from the shell?). > > -Peff Yes, that's what the asciinema does – it pipes git clone --progress to a script, and that's pretty much it. That's why I thought about a core.pipe option, that would hold the my-progress-scrapper command. That's a very easy change, could it be added to git source code? The scrapper from the asciinema doesn't care if it's count, retrieve or resolve, etc. currently ongoing, it simply displays a gauge with the current percentage for the current stage. After a while one discovers that it's resolve that's the final stage, and the gauge is intuitive either before or after this revelation. -- Best regards, Sebastian Gniazdowski
