Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!tcdcs!swift.cs.tcd.ie!vax1.tcd.ie!ecarroll From: ecarroll@vax1.tcd.ie (Eddy Carroll) Newsgroups: comp.sys.amiga.tech Subject: Re: ls 4.0k Case Sensitive Message-ID: <6878.26fe0ccf@vax1.tcd.ie> Date: 24 Sep 90 13:40:31 GMT References: <1928@lpami.wimsey.bc.ca> <1990Sep6.034821.9389@ecn.purdue.edu> <82=R02Cb02ds01@JUTS.ccc.amdahl.com> Organization: Computer Laboratory, Trinity College Dublin Lines: 28 > The subsequent version (v5.0k ?) will be 2.0 only, and will support links (if > they're actually "in there"), and will use the new file scanning calls, etc. > It will NOT perform wildcard expansion internally, but will leave that chore > up to the shell where it really belongs (IMO). That is, it will NOT do so, > if the command-line length limitation has truly been overcome, and has a limit > that is some "reasonable" value (say 32K ... yes, I do have dirs with a couple > thousand files in them ... USENET articles do pile up, ya know). And with > that change, the -M flag will be history, of course. > > Comments? > > /kim Since (1) the current AmigaShell 2.0 doesn't support wildcard expansion on the command line (which I agree is a nice place to have it), and (2) AmigaDos 2.0 has calls to do wildcard expansion for you, I'd argue quite strongly for leaving in wildcard support. Particularly since there are no 2.0-specific enhanced shells available as yet, to do the wild card expansion instead. My suggestion for 4.1 (4.0 is great, by the way) is a flag to say that the shell has done the wildcard expansion, so that I don't get a long listing when I do ls * in my shell (which is not yet sksh). Just my $.02. -- Eddy Carroll ----* Genuine MUD Wizard | "You haven't lived until ecarroll@vax1.tcd.ie | you've died in MUD!" ecarroll%vax1.tcd.ie@cunyvm.cuny.edu | -- Richard Bartle