git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogan Dawes <lists@dawes.za.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: 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: Wed, 15 Aug 2007 23:22:04 +0200	[thread overview]
Message-ID: <46C36E7C.1080501@dawes.za.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0708151708570.19222@wbgn129.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:

> Hmm.  Somehow I doubt that this hack works _outside_ of the Windows 
> console.  I.e. if you call git in rxvt, it will fail, if you ssh into 
> Windows, it will fail.
> 
> Ciao,
> Dscho
> 

I'd say that since Windows doesn't have the concept of terminfo or 
terminal types, and since SSH is mostly only supported through 
cygwin-style "hacks", (or F-Secure, but I have no experience with that) 
that we should not be _too_ concerned about that.

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.

My R0.02.

Regards,

Rogan

  reply	other threads:[~2007-08-15 21:23 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 [this message]
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=46C36E7C.1080501@dawes.za.net \
    --to=lists@dawes.za.net \
    --cc=Johannes.Schindelin@gmx.de \
    --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).