All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@debian.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Nicolas Pitre <nico@cam.org>, git@vger.kernel.org
Subject: Re: That new progress meter
Date: Sat, 03 Nov 2007 13:09:53 +0100	[thread overview]
Message-ID: <20071103120953.GC13417@artemis.corp> (raw)
In-Reply-To: <Pine.LNX.4.64.0711021836000.4362@racer.site>

[-- Attachment #1: Type: text/plain, Size: 2134 bytes --]

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.
    * refs/remotes/origin/html: fast forward to branch 'html' of git://git.kernel.org/pub/scm/git/git
      old..new: 1c70883..7ae0ab2
    * refs/remotes/origin/maint: fast forward to branch 'maint' of git://git.kernel.org/pub/scm/git/git
      old..new: 136e631..f45e867
    * refs/remotes/origin/man: fast forward to branch 'man' of git://git.kernel.org/pub/scm/git/git
      old..new: 9850e2e..44dd7e0
    * refs/remotes/origin/master: fast forward to branch 'master' of git://git.kernel.org/pub/scm/git/git
      old..new: 3e4bb08..e3d6d56
    * refs/remotes/origin/next: fast forward to branch 'next' of git://git.kernel.org/pub/scm/git/git
      old..new: a93d0b0..536f64a
    * refs/remotes/origin/pu: forcing update to non-fast forward branch 'pu' of git://git.kernel.org/pub/scm/git/git
      old...new: eb57be8...bf1284a

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. 
Erase Start of Line     <ESC>[1K
    Erases from the current cursor position to the start of the current line. 
Erase Line              <ESC>[2K
    Erases the entire current line.

  [0] http://www.termsys.demon.co.uk/vtansi.htm

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-11-03 12:10 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 [this message]
2007-11-03 14:53   ` Nicolas Pitre
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=20071103120953.GC13417@artemis.corp \
    --to=madcoder@debian.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.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 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.