From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from math.gatech.edu (euclid.skiles.gatech.edu [130.207.146.50]) by werple.net.au (8.7/8.7.1) with SMTP id KAA03948 for <mason@werple.mira.net.au>; Sat, 11 Nov 1995 10:17:10 +1100 (EST)
Received: by math.gatech.edu (5.x/SMI-SVR4)
	id AA16804; Fri, 10 Nov 1995 18:04:39 -0500
Resent-Date: Fri, 10 Nov 1995 16:05:20 -0700
Old-Return-Path: <mdb@cdc.noaa.gov>
Date: Fri, 10 Nov 1995 16:05:20 -0700
Message-Id: <9511102305.AA06309@suomi.cdc.noaa.gov>
From: Mark Borges <mdb@cdc.noaa.gov>
To: ZSH mailing list <zsh-workers@math.gatech.edu>
Subject: rmstar option nit in 2.6-beta11
Organization: CIRES, University of Colorado
X-Attribution: mb
Resent-Message-Id: <"bAATs1.0.U64.6gzem"@euclid>
Resent-From: zsh-workers@math.gatech.edu
X-Mailing-List: <zsh-workers@math.gatech.edu> archive/latest/590
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu

I'm one of the fools who aliases rm to 'rm -i' and who has zsh prompt
on *. (I know the argument that I'll be burned when I do an rm * on
another system and expect to be protected. But until then I'll just
attend `rm -i anonymous meetings' ;-)

Anyway, should zsh behave this way under these circumstances:

	$ rm *
	zsh: sure you want to delete all the files in /foo/bar? n
	rm: too few arguments
	Try `rm --help' for more information.

(this is gnu rm, obviously)

I'd thought the command itself would be aborted, but instead it
appears to just clean out the arg list for the command. Is this the
intended behaviour?

  -mb-