All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: A nice, beauty progress metter for Git Clone + a feature request
Date: Mon, 27 Mar 2023 10:59:56 +0000	[thread overview]
Message-ID: <CAKc7PVDZ4Ra7s-pyFms1-sGqjYD9b407G1u0A0hHTkQRa-MPkQ@mail.gmail.com> (raw)
In-Reply-To: <ZBIIKqAIF+aF8vvx@coredump.intra.peff.net>

On Wed, 15 Mar 2023 at 18:02, Jeff King <peff@peff.net> 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

  reply	other threads:[~2023-03-27 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKc7PVD_65vB5+meeO3xcu4ASbqr85LBGUO8Ntb7SvbO+NNHmQ@mail.gmail.com>
2023-03-10 11:37 ` A nice, beauty progress metter for Git Clone + a feature request Sebastian Gniazdowski
2023-03-15 18:02   ` Jeff King
2023-03-27 10:59     ` Sebastian Gniazdowski [this message]
2023-03-28 17:51       ` Jeff King
2023-03-28 20:49         ` Sebastian Gniazdowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKc7PVDZ4Ra7s-pyFms1-sGqjYD9b407G1u0A0hHTkQRa-MPkQ@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.