X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Matthew Woehlke Subject: OT: tcsh and LS_COLORS (was: Problems with 'dircolors') Date: Thu, 12 Oct 2006 12:41:55 -0500 Lines: 19 Message-ID: References: <452D8F8D.4010103@byu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 In-Reply-To: <452D8F8D.4010103@byu.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 Eric Blake wrote: > Oh, by the way, if you use tcsh, be aware that it also uses the LS_COLORS > environment variable internally, but that it does not understand quite as > many options as ls does and gripes about what it doesn't understand, which > is why I had to patch the cygwin version of LS_COLORS to silence stderr > during the tcsh eval. Hopefully, a newer release of tcsh will allow me to > remove that hack from coreutils. That's all? I had to build a hand-patched tcsh across our platform list because the unpatched sources *won't run* if tcsh doesn't understand LS_COLORS. And some csh's have the same behavior. IOW you couldn't run [t]csh *at all* with the newer LS_COLORS features. Anyway, just wondering if you've also seen this and what if anything has been done to Cygwin's tcsh to cope. -- Matthew "I don't question your existence -- God" (seen on a church billboard) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/