Re: CR codes from git commands

From: Brent Goodrick <bgoodr@gmail.com>
Date: Jan 22, 2009, 04:00 UTC
Message-ID: <e38bce640901212000w5b1b8a91tfdd0abbebde162a0@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0901211636340.3586@pacific.mpi-cbg.de>

On Wed, Jan 21, 2009 at 7:38 AM, Johannes Schindelin

> In my test I performed one minute ago, "git pull | cat" did not show any
> CR.  Maybe it is the "git" instead of "get" :-)

<snip>

Show 12 quoted lines

> > Thanks.  The fix should be to arrange it so that I can set something so
> > that a bare call such as (but just "git pull"):
> >
> >   git pull
> >
> > will emit no CR codes at all, ever, regardless of if there is a tty.
> > Even if it is an env var, but a config setting would be ok too.
>
> I would actually think that it should not be an env var or config setting
> if piping it to "cat" does what you want: if the output is a tty, I think
> it is safe to assume that you want to see the progress, and if you don't,
> "| cat" is not an unreasonable thing to ask for.

You might not be able to see those CR codes from your terminal, because ... well ... its a terminal which will process them. And if you can't reproduce it in your environment, you'll have to duplicate my environment, and at that is well beyond what I would ask anyone to do. Thanks for your effort in looking into it. If I get annoyed enough with it, I'll debug the code myself and propose a patch (but don't hold your breath because I'm still learning this complex tool).

Thanks! Brent