Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!sharkey!atanasoff!jwright From: jwright@atanasoff.cs.iastate.edu (Jim Wright) Newsgroups: comp.sys.amiga Subject: Re: Wild Cards, file syntax Message-ID: <805@atanasoff.cs.iastate.edu> Date: 16 Feb 89 23:50:26 GMT References: <8902131846.AA21527@postgres.Berkeley.EDU> <35960@bbn.COM> <5985@cbmvax.UUCP> Sender: jwright@atanasoff.cs.iastate.edu Reply-To: jwright@atanasoff.cs.iastate.edu (Jim Wright) Organization: Iowa State U. Computer Science Department, Ames, IA Lines: 44 In article <5985@cbmvax.UUCP> higgin@cbmvax.UUCP (Paul Higginbottom MKT) writes: }In article deven@pawl.rpi.edu (Deven Corzine) writes: }$I still find some definite problems with the AmigaDOS method of file }$system structuring. I find "." and ".." far easier to use }$effectively, even if they are more to type. "" as current directory }$is obnoxious, if you ask me. Me too. }As someone else mentioned; it's mainly a question of what you're used to. So why should the Amiga be the only one different? Yes, it is an easy translation, but can't you think of a few more important bits of information to stash away in your long-term memory? I'd think that using a convention which already exists, and which people are accustomed to, is a good marketing strategy. (Sorry :-) }$There is no easy equivilent for "./file" under AmigaDOS... } }This is surely rather unimportant as the current directory is usually }searched FIRST anyway. From the WShell manual: The full search heirarchy followed by WShell is * The Previous Command * Resident Commands * Built-in Commands * REXX-Language Macro Programs * An Implicit Directory --> * The Current directory * The Local Path Directories * The Global Path Directories. I won't argue the use of the word "usually". Shall we agree that there are many situations where having an equivalent for "./file" is important? }$I don't understand at all the objection to Unix wildcards. } }Neither do I, except I find "." files obnoxious, i.e., "*" doesn't }match them so to clean out a directory with some files which start with }. you have to do "rm * .*" (don't you?). If you want to delete the directory, go down one level and type "rm -r dirname". This will take care of "*", ".*", and subdirectories too. Nasty sort of a command. :-)