X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=3.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT X-Spam-Check-By: sourceware.org Date: Wed, 29 Feb 2012 23:37:32 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1752751347.20120229233732@mtu-net.ru> To: Earnie Boyd , cygwin@cygwin.com Subject: Re: Cygwin errors after altering Windows command prompt shortcut (???) In-Reply-To: References: <1409797345.20120229030537@mtu-net.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Greetings, Earnie Boyd! >> (Off topic:  Huh.  So maybe git or msysgit was monkeying around with >> the color table...maybe using a non-standard color?) > The MSYS part of msysgit doesn't muck with registry keys. Maybe > something with tksh that it uses does. I think it was his own hands. Windows console colors assignment dialogue have a long-standing behavioral issues, that can impact the end result, if you're unaware of them. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 29.02.2012, <23:35> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple