Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpfcso!hpfelg!koren
From: koren@hpfelg.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Re:  ls 4.0k Case Sensitive (was Re:   CygnusEd Pro)
Message-ID: <13920094@hpfelg.HP.COM>
Date: 21 Sep 90 14:24:57 GMT
References: <dick.4313@woodwrk.LoneStar.ORG>
Organization: HP Elec. Design Div. -FtCollins
Lines: 38

> As I recall, ls 4.0k has a switch to enable/disable case sensitivity, and is

> As for the SKsh/Wshell question, is it possible that you are using SKsh's
> builtin ls when you are running that shell?  That is the only explanation
> that comes to mind.

This poster has a good point as well; you may be using the builtin SKsh
"ls" command, which will happen by default unless you configure it another
way.

You can make SKsh *completely* forget about its own ls command by saying:

   unset -b ls

From then on, any references to "ls" will use an alias, if you have one,
or a function if you have one, or the external one failing either of those.

Another way to play with the external "ls" without unsetting the SKsh
internal "ls" is to say:

   alias ls=$(which ls)

Then, any references to "ls" will use the SKsh alias, which will point
to the external command.

The ls 4.0k command provides many more options and configurations than
the internal SKsh ls does.  You can make ls 4.0k into a resident command
using:

   resident -a $(which ls)

from within SKsh.  That, coupled with the "unset -b ls" and "dwclist -a ls"
above, will let you use Kim's "ls" with little invocation overhead while
letting ls 4.0k expand wildcards.

Hope this helps,

   - steve