From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: msclrhd@googlemail.com
Cc: msysGit <msysgit@googlegroups.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [msysGit] Re: Need your help with MinGW Issue 17: --color options don't work (produce garbage)
Date: Wed, 15 Aug 2007 01:03:25 -0700 [thread overview]
Message-ID: <a1bbc6950708150103v35330b47o781fb5d74e3d9aef@mail.gmail.com> (raw)
In-Reply-To: <3f4fd2640708150032l7441b285mc2cc9e22702bce21@mail.gmail.com>
On 8/15/07, Reece Dunn <msclrhd@googlemail.com> wrote:
>
> On 15/08/07, Dmitry Kakurin wrote:
> > Here are the facts:
> >
> > 'git branch --color' produces garbage:
> > $ git branch --color
> > devel←[m
> > dima←[m
> > dmitryk←[m
> > * ←[32mmaster←[m
> > mob←[m
> > next←[m
> >
> > 'git branch --color | cat' produces expected colored output.
> >
> > I've traced it down to printf statement in gdb and it sends the right
> > esc-sequence.
> > Where should I look next?
>
> Windows doesn't recognise the *nix printf colour codes.
>
> Piping through cat will be going through cygwin/mingw emulation,
> translating the colour codes to the correct API calls.
That's my question. If there is a way to build cat.exe to do this kind
of emulation under MinGW then I should be able to do the same for
git.exe.
I hope I just need to #define something while building Git.
But what is it?
--
- Dmitry
next prev parent reply other threads:[~2007-08-15 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 6:29 Need your help with MinGW Issue 17: --color options don't work (produce garbage) Dmitry Kakurin
2007-08-15 7:32 ` Reece Dunn
2007-08-15 8:03 ` Dmitry Kakurin [this message]
2007-08-15 8:31 ` [msysGit] " Reece Dunn
2007-08-15 22:07 ` Dmitry Kakurin
2007-08-15 15:10 ` Johannes Schindelin
2007-08-15 21:22 ` Rogan Dawes
2007-08-15 21:34 ` Junio C Hamano
2007-08-15 22:04 ` Rogan Dawes
2007-08-21 14:08 ` Rogan Dawes
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=a1bbc6950708150103v35330b47o781fb5d74e3d9aef@mail.gmail.com \
--to=dmitry.kakurin@gmail.com \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
--cc=msysgit@googlegroups.com \
/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).