From: Rogan Dawes <lists@dawes.za.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Reece Dunn <msclrhd@googlemail.com>,
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: Thu, 16 Aug 2007 00:04:19 +0200 [thread overview]
Message-ID: <46C37863.4020203@dawes.za.net> (raw)
In-Reply-To: <7vsl6ko51b.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Rogan Dawes <lists@dawes.za.net> writes:
>
>> Users that *do* need to use rxvt or SSH should simply disable the
>> color mode, or alternatively, use the cygwin version. Color, while
>> useful, is hardly critical functionality.
>
> Heh, that almost suggests that the native Windows command.com
> support can disable the color without upsetting anybody ;-)
>
If that is the easiest way, yes.
I *do* think that trying to get color working on the DOS cmdline is a
worthy goal. I just don't think it is worth overcomplicating the issue
and trying to handle rare corner cases such as someone SSHing into a
Windows box, or running CMD inside rxvt.
One approach that might be more compatible with the existing escape code
approach is to define the appropriate ANSI color escape sequences. Ah, a
bit more googling shows that cmd.exe doesn't handle ANSI sequences in
Windows NT and later.
Regards,
Rogan
next prev parent reply other threads:[~2007-08-15 22:05 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
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 [this message]
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=46C37863.4020203@dawes.za.net \
--to=lists@dawes.za.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).