On 09.05.2010 22:26, Rick Pasotto wrote:
> What did I update recently that caused me to lose ls coloring with this
> error message:
>
> ls: unrecognized prefix: hl
> ls: unparsable value for LS_COLORS environment variable
>
> How should I fix it?
>
Using lenny here, but it has been set in .bashr
On 05/09/2010 10:26 PM, Rick Pasotto wrote:
What did I update recently that caused me to lose ls coloring with this
error message:
ls: unrecognized prefix: hl
ls: unparsable value for LS_COLORS environment variable
How should I fix it?
Hi,
looks like coreutils bug
http://bugs.debian.org/cgi-
Just type source .bashrc
Sent from my BlackBerry®
-Original Message-
From: Rick Pasotto
Date: Sun, 9 May 2010 17:48:56
To:
Subject: Re: colorized ls
On Sun, May 09, 2010 at 04:44:08PM -0500, Ron Johnson wrote:
> On 05/09/2010 03:26 PM, Rick Pasotto wrote:
> >What did I update
On 05/09/2010 04:48 PM, Rick Pasotto wrote:
On Sun, May 09, 2010 at 04:44:08PM -0500, Ron Johnson wrote:
On 05/09/2010 03:26 PM, Rick Pasotto wrote:
What did I update recently that caused me to lose ls coloring with this
error message:
What exactly (Stable, Testing, Sid) did you update, and w
On Sun, May 09, 2010 at 04:44:08PM -0500, Ron Johnson wrote:
> On 05/09/2010 03:26 PM, Rick Pasotto wrote:
> >What did I update recently that caused me to lose ls coloring with this
> >error message:
>
> What exactly (Stable, Testing, Sid) did you update, and what command
> did you use to update i
On 05/09/2010 03:26 PM, Rick Pasotto wrote:
What did I update recently that caused me to lose ls coloring with this
error message:
What exactly (Stable, Testing, Sid) did you update, and what command
did you use to update it?
ls: unrecognized prefix: hl
ls: unparsable value for LS_COLORS en
On Sun, May 09, 2010 at 10:33:23PM +0200, d.sastre.med...@gmail.com wrote:
> On Sun, May 09, 2010 at 04:26:36PM -0400, Rick Pasotto wrote:
> > What did I update recently that caused me to lose ls coloring with this
> > error message:
> >
> > ls: unrecognized prefix: hl
> > ls: unparsable value for
On Sun, May 09, 2010 at 04:26:36PM -0400, Rick Pasotto wrote:
> What did I update recently that caused me to lose ls coloring with this
> error message:
>
> ls: unrecognized prefix: hl
> ls: unparsable value for LS_COLORS environment variable
>
> How should I fix it?
In academic interest you can
On Sun, May 09, 2010 at 04:26:36PM -0400, Rick Pasotto wrote:
> What did I update recently that caused me to lose ls coloring with this
> error message:
>
> ls: unrecognized prefix: hl
> ls: unparsable value for LS_COLORS environment variable
>
> How should I fix it?
If you are using system-wide
What did I update recently that caused me to lose ls coloring with this
error message:
ls: unrecognized prefix: hl
ls: unparsable value for LS_COLORS environment variable
How should I fix it?
--
"I am only one. But I am one. I cannot do everything but I can do
something. And I will not let wha
On Wed, Jan 05, 2005 at 07:49:01PM -0600, David Dyer-Bennet wrote:
> And the other problem there is that /usr/doc/fileutils and
> the info pages don't seem to give me any clue where to report bugs
> to.
The debian BTS in the first instance (e.g. via reportbug) - then the bug can
be sent upstream
The default setup seems to alias ls to ls --color. When this is run
in an emacs shell window (on a character cell terminal in my test;
though I think it does the same thing under X), the output comes out
colorized -- even though the terminal type is set to DUMB there, and
DUMB isn't on the list of
12 matches
Mail list logo
