From: Nicolas Pitre <nico@cam.org>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: That new progress meter
Date: Sat, 03 Nov 2007 10:53:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711031042390.21255@xanadu.home> (raw)
In-Reply-To: <20071103120953.GC13417@artemis.corp>
On Sat, 3 Nov 2007, Pierre Habouzit wrote:
> On Fri, Nov 02, 2007 at 06:36:35PM +0000, Johannes Schindelin wrote:
> > Hi Nico,
> >
> > that new progress meter sure is amazing and useful!
>
> I do agree. There seems to be some glitches though, here is how my
> output looks after a git fetch I just did on git.git:
>
> remote: Generating pack...
> remote: Done counting 310 objects.
> remote: Deltifying 310 objects... | Here we have a glitch |
> remote: 100% (310/310) done `-------vvvv----------'
> remote: Total 310 (delta 160), reused 178 (delta 112)iB/s
> Receiving objects: 100% (310/310), 379.98 KiB | 136 KiB/s, done.
> Resolving deltas: 100% (160/160), done.
I know. This is why i TRIED TO KEEP THE "Receiving objects" line as
short as possible.
> FWIW, maybe instead using spaces to erase lines we could use minimal
> vt100 codes[0] like:
>
> Erase End of Line <ESC>[K
> Erases from the current cursor position to the end of the current line.
I thought about that too, but this is not perfectly portable to all
terminals according to a quick glance at /etc/termcap. Does the Windows
console support it? Also we might prefer not to rely on termcap/terminfo
library calls.
The other solution is to make the remote object summary line a bit
longer, but this will be effective only when remote servers are
upgraded. Might that be good enough?
Nicolas
next prev parent reply other threads:[~2007-11-03 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 18:36 That new progress meter Johannes Schindelin
2007-11-03 12:09 ` Pierre Habouzit
2007-11-03 14:53 ` Nicolas Pitre [this message]
2007-11-03 16:09 ` Alex Riesen
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=alpine.LFD.0.9999.0711031042390.21255@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).