Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: CLI Java Glitch References: <4dffe2ea$0$57121$c30e37c6@exi-reader.telstra.net> <7ba20719biasrlu0druv0dta3midgp9bl8@4ax.com> <4e28cb1a$0$308$14726298@news.sunsite.dk> <4e2937a0$0$46569$c30e37c6@exi-reader.telstra.net> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: 25 Jul 2011 11:25:51 GMT Lines: 16 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1311593151 tunews.univie.ac.at 71616 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6531 Esmond Pitt wrote: > On 22/07/2011 11:14 AM, Peter Duniho wrote: >>> It is the file system and the command interpreter (shell in >>> *nix terminology). >> Huh? Inasmuch as the file system can be accessed, and case-sensitivity >> observed, without a command interpreter, I don't see why you are >> dragging the command interpreter into it. > I have to agree with that. I can't see what the command interpreter has > to do with this at all. My guess would be, that for consistency it is preferable, that (CLI) shells follow the system's typical case in- or sensitivity even for its internal commands: cmd.exe: cd, cD, Cd or CD *nix shells: only cd Still, just a marginal relation.