From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: "Reece Dunn" <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 15:07:18 -0700 [thread overview]
Message-ID: <a1bbc6950708151507l15de5e9br5a09f13ad21d7f41@mail.gmail.com> (raw)
In-Reply-To: <3f4fd2640708150131o7578c2efy806891fc3def7429@mail.gmail.com>
On 8/15/07, Reece Dunn <msclrhd@googlemail.com> wrote:
> I don't believe that MinGW has got this working for cat, that is why
> one that supports colours on Windows needs to be written.
MSys' cat does support colors even when I run it from cmd.exe.
I've looked at sources for cat on mingw.sourceforge.com and (as
expected) there is no code to handle esc-sequences.
That would be insane - too many utilities like ls, diff, cat, less
etc. do that. So there is obviously a library for this.
I've tried to "parse" makefiles for cat, but they are so huge and I
know about gcc/make on Unix so little that I was unable to find the
secret sauce.
I've also asked this question on MinGW list so I'm waiting for reply.
--
- Dmitry
next prev parent reply other threads:[~2007-08-15 22:07 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 ` [msysGit] " Dmitry Kakurin
2007-08-15 8:31 ` Reece Dunn
2007-08-15 22:07 ` Dmitry Kakurin [this message]
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=a1bbc6950708151507l15de5e9br5a09f13ad21d7f41@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).