Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!sdcrdcf!ism780c!mikep From: mikep@ism780c.UUCP (Michael A. Petonic) Newsgroups: comp.unix.wizards Subject: Re: more rm insanity Message-ID: <8145@ism780c.UUCP> Date: Sun, 6-Dec-87 02:31:00 EST Article-I.D.: ism780c.8145 Posted: Sun Dec 6 02:31:00 1987 Date-Received: Fri, 11-Dec-87 06:14:48 EST References: <1257@boulder.Colorado.EDU> <6840002@hpcllmv.HP.COM> Reply-To: mikep@ism780c.UUCP (Michael A. Petonic) Organization: Interactive Systems Corp., Santa Monica CA Lines: 26 In article <1895@celtics.UUCP> roger@celtics.UUCP (Roger B.A. Klorese) writes: >My point, really, is that we need some way of determining in a command >line which patterns are *filenames* - these should be expanded by the >shell - and which are *(option patterns, network-node wildcards, etc.)* - >things which cannot be expanded or pattern-matched against a directory, >and should be passed to the program for expansion. Hey, wait a minute. This is easily accomplished... Use the backslash. I know, I know, the backslash is usually located out of the way, but that's a wimpy excuse. I couldn't see adding a "feature" like smart expansion and thoroughly modifying the shell (and possibly the kernel) just to make things slightly simpler for a select few. The rest of us are used to globbing in the shell and use the backslash when we don't want globbing. No problem. -MikeP -------- Michael A. Petonic (213) 453-8649 x3247 INTERATIVE Systems Corporation "My opinions in no way influences 2401 Colorado Blvd. the price of tea in China." Santa Monica, CA. 90404 {sdcrdcf|attunix|microsoft|sfmin}!ism780c!mikep