Debian Bug report logs - #479544
dircolors: please eliminate duplicates before writing variable

Full log

Message #8 received at [email protected] (full text, mbox, reply):

Received: (at 479544) by bugs.debian.org; 5 May 2008 17:29:29 +0000
From [email protected] Mon May 05 17:29:29 2008
X-Spam-Checker-Version: SpamAssassin 3.1.4-bugs.debian.org_2005_01_02 
	(2006-07-26) on rietz.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=4.0 tests=BAYES_00,FOURLA,
	HAS_BUG_NUMBER autolearn=no version=3.1.4-bugs.debian.org_2005_01_02
Return-path: <[email protected]>
Received: from mx.meyering.net ([82.230.74.64])
	by rietz.debian.org with esmtp (Exim 4.63)
	(envelope-from <[email protected]>)
	id 1Jt4VE-0000Ub-RV
	for [email protected]; Mon, 05 May 2008 17:29:29 +0000
Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000)
	id 5C45E5B19C; Mon,  5 May 2008 19:29:27 +0200 (CEST)
From: Jim Meyering <[email protected]>
To: martin f krafft <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: Bug#479544: dircolors: please eliminate duplicates before writing variable
In-Reply-To: <[email protected]> (martin f. krafft's
	message of "Mon, 5 May 2008 13:21:22 +0100")
References: <[email protected]>
Date: Mon, 05 May 2008 19:29:27 +0200
Message-ID: <[email protected]>
Lines: 31
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

martin f krafft <[email protected]> wrote:
> Package: coreutils
> Version: 6.10-6
> Severity: wishlist
> File: /usr/bin/dircolors
>
> If I specify a filetype twice in the dircolors file, the resulting
> LS_COLORS will have the entry twice:
>
>   lapse:/% echo "EXEC 00\nEXEC 01" | dircolors -
>   LS_COLORS='ex=00:ex=01:';
>   export LS_COLORS
>
> While /bin/ls works fine with it and prefers the last setting over
> previous ones, e.g. zsh's completion system works the other way.
>
> I realise I could be filing this as a bug against zsh, but that
> would be asking zsh to work around a shortcoming in the dircolors
> "API".
>
> Instead, would it be possible to fix dircolors so that it eliminates
> earlier entries if the dircolors file overrides entries for a given
> file class?
>
> The rationale is that I need dircolors --print-database output in my
> own dircolors file if I don't want to hardcode defaults by hand. If
> I do that, I'd prefer to keep customisation separate.

Good idea.
If no one volunteers to do this soon
I'll put it on the TODO list.

Send a report that this bug log contains spam.