From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8d472879e3f609e0
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-06-07 21:14:22 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!snoopy.risq.qc.ca!chi1.webusenet.com!news.webusenet.com!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!53ab2750!not-for-mail
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5a) Gecko/20030529
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Case sensitivity (was Re: no title)
References: <mailman.8.1054540581.12990.comp.lang.ada@ada.eu.org>
 <slrnbdm1i7.1k5.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <bbf9kl$7kt$1@ns.felk.cvut.cz>
 <20619edc.0306021018.6ee4dd09@posting.google.com> <c5jhbb.0sd.ln@skymaster>
 <1054649187.11497@master.nyc.kbcfp.com>
 <20619edc.0306031034.6a2f5f25@posting.google.com>
 <1054666439.685312@master.nyc.kbcfp.com>
 <slrnbdrj6f.i5.randhol+abuse@kiuk0152.chembio.ntnu.no>
 <1054735867.264510@master.nyc.kbcfp.com>
 <QsyEa.15733$JA5.305118@news.xtra.co.nz>
In-Reply-To: <QsyEa.15733$JA5.305118@news.xtra.co.nz>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <xKyEa.45844$ca5.11517@nwrdny02.gnilink.net>
Date: Sun, 08 Jun 2003 04:14:21 GMT
NNTP-Posting-Host: 162.84.224.133
X-Complaints-To: abuse@verizon.net
X-Trace: nwrdny02.gnilink.net 1055045661 162.84.224.133 (Sun,
 08 Jun 2003 00:14:21 EDT)
NNTP-Posting-Date: Sun, 08 Jun 2003 00:14:21 EDT
Xref: archiver1.google.com comp.lang.ada:38807
Date: 2003-06-08T04:14:21+00:00
List-Id: <comp.lang.ada>

AG wrote:
> I'm not an experienced Unix guru so I have
> to try and see if a command works. So I type
> something like:  x/yz - doesn't work. So I type
> X/yz - still doesn't work. So I call in an expert
> who tells me that it should be x/Yz (not X/Yz
> which I've also tried). When questioned *why*,
> the answer is a shrug and a simple reply "that's Unix"

You could try reading the manual. (Also, x/yz is not like
any UNIX command, so you have boiled down the original
problem beyond anything that an experienced UNIX guru
could explain to you correctly.) UNIX command names are
nearly always lower case, but their option may be of
both cases, especially when there are many.

One clever case where the convention was violated was in the
name of the debugger on some UNIX system I used, SCO I think.
It came in two flavors, "dbxtra" and "dbXtra". The former
invoked a command-line version that ran in a terminal session,
while the latter ran using a GUI (under X Window, hence the name).