From: Mark Borges <mdb@cdc.noaa.gov>
To: ZSH mailing list <zsh-workers@math.gatech.edu>
Subject: rmstar option nit in 2.6-beta11
Date: Fri, 10 Nov 1995 16:05:20 -0700 [thread overview]
Message-ID: <9511102305.AA06309@suomi.cdc.noaa.gov> (raw)
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-
next reply other threads:[~1995-11-10 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-10 23:05 Mark Borges [this message]
1995-11-10 23:45 ` Richard Coleman
1995-11-11 0:12 ` Barton E. Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9511102305.AA06309@suomi.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).