Path: utzoo!attcan!uunet!husc6!mailrus!cornell!uw-beaver!teknowledge-vaxc!sri-unix!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.unix.wizards
Subject: Re: fixing rm * (was: Worm/Passwords)
Message-ID: <727@quintus.UUCP>
Date: 23 Nov 88 06:09:49 GMT
References: <22401@cornell.UUCP> <4627@rayssd.ray.com> <8563@rpp386.Dallas.TX.US> <125@embossed.UUCP> <672@quintus.UUCP> <1232@atari.UUCP> <812@hadron.UUCP>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 14

In article <812@hadron.UUCP> jsdy@hadron.UUCP (Joseph S. D. Yao) writes:
[about rm *]
>What I did, a decade ago, was to have a list of _commands_ which the
>shell, after calling glob, would always prompt for after printing out
>the entire expanded command line.  The list included "rm" and "rmdir".
>No prompting if "glob" was not called.

Nice one, but how does this handle user commands with similar properties?
(For example, "a.rm".)
One answer, of course, would be to have a
	GLOBASK=rm:rmdir
shell variable, so that one could put
	GLOBASK=a.rm:$GLOBASK
in ones .profile.  (Did I just make a constructive suggestion?  Oops.)