Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.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: <13920092@hpfelg.HP.COM>
Date: 21 Sep 90 14:15:27 GMT
References: <dick.4313@woodwrk.LoneStar.ORG>
Organization: HP Elec. Design Div. -FtCollins
Lines: 29

> >Your problem may be at least partially due to the fact that ls 4.0 is
> >case-sensitive. I went back to 3.2 (I think) because of this.
> >
> From a(n) SKsh 1.4 window ls 4.0k is *NOT* case sensitive.  I just
> experimented a bit and found that Mark is correct, however.  From a Wshell
> window ls 4.0k *IS* case sensitive.  What's the deal?  (Steve?)

Both SKsh and ls 4.0k have different options to handle case sensitivity,
and these options can interact in interesting ways.  However, there is
enough flexibility to make them act almost any way you want.

First of all, in SKsh 1.5 (not 1.4!) you have a choice about whether to
let SKsh expand the wildcards on the command line, or have ls do it.
(See the dwclist command for details on that - again, only in >= 1.5).
If you let SKsh expand wildcards, then case sensitivity will be controlled
by SKsh: ie, you can turn it off or on with an SKsh option (see the options
command).  If you let ls expand the wildcards by putting ls in your dwclist,
(generally a good idea), then case sensitivity will be controlled by
ls (and I believe you can turn case sensitivity on or off there as well).
I don't know how WShell handles case sensitivity, and whether it is
configurable in this regard, so I can't help you there.  (I should
really buy this and play with it someday...)

In short, you can make it work however you want, but you have to set it
up that way.  The default may not be what you like.

Hope this helps!

    - steve