X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	Steve Kelem <skelem AT elementcxi DOT com>, Cygwin <cygwin AT cygwin DOT com>,
	ebb9 AT byu DOT net
Subject:	Re: dircolors generates "uknown colorls variable su" [attn tcsh maintainer]
Date:	Tue, 17 Jan 2006 18:00:33 +0000
Message-Id:	<011720061800.18434.43CD30C1000ED6000000480222007601800A050E040D0C079D0A@comcast.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> I upgraded to coreutils-5.93-2, and now when I run
> eval `dircolors -csh`
> I get
> Unknown colorls variable `su'.

Hmm, this is an upstream issue.  'man tcsh' documents that
LS_COLORS is a magic environment variable to the shell, and
by default, tcsh 6.14.00 does not recognize the su= code for
setuid variables, even though dircolors 5.93 now outputs
this category.  People using tcsh without patches suffer
from version mismatch between what dircolors outputs
for use by coreutils' ls, vs. what tcsh parses for use in the
shell builtin ls-F.

I personally don't use tcsh, and I am surprised that no one
else has reported this issue upstream to coreutils; I will
go ahead and raise that issue.  For now, the workaround
is to provide your own file for dircolors' use to avoid the
SETUID category:

eval "`dircolors --csh path/to/your/DIR_COLORS`"

--
Eric Blake
volunteer cygwin coreutils maintainer

--
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/

- Raw text -