Re: [PATCH] fix display overlap between remote and local progress

From: Marcin Cieslak <saper@saper.info>
Date: Mar 30, 2012, 14:56 UTC
Message-ID: <slrnjnbic3.30f0.saper@saper.info>
In-Reply-To: <Pine.LNX.4.64.0711041331520.4362@racer.site>

(This is about ANSI clear-eol sequence introduced to sideline.c in commit
 ebe8fa738dcf6911fe520adce0cfa0cb26dee5e2)

Show 12 quoted lines

>> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Sun, 4 Nov 2007, Nicolas Pitre wrote:
>
>> +#define SUFFIX "\e[K"  /* change to "        " if ANSI sequences don't work */ 
>
> I am almost certain (without even testing) that cmd.exe has problems with 
> that.  It does not even understand colorisation.
>
> My vote is to let it be for the moment, and us msysGit people will 
> probably add something like NO_ANSI_TERM=YesPlease later.

Hi,

We are using script(1) to record the workflow and troubleshoot problems. script utility records all control codes as well (actually everything that passes via pseudoterminal it creates.

We managed to get git quiet on most control codes with color.ui=false and pager set to nothing, but we still get ESC [ K codes from the remote output (we are using gerrit and it generates some).

While I can live with git progress output lines in the log, it's quite annoying to edit those ANSI sequences out of the script. One has to remember to set TERM=dumb before invoking _some_ git operations.

Is there any better solution possible?

//Marcin