Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Reasons for not wanting EXTENDED_GLOB interactively (was Re: PATCH:...)
- X-seq: zsh-workers 8175
- From: Bruce Stephens <bruce@xxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Reasons for not wanting EXTENDED_GLOB interactively (was Re: PATCH:...)
- Date: 07 Oct 1999 21:32:19 +0100
- In-reply-to: Zefram's message of "Thu, 7 Oct 1999 18:29:43 +0100 (BST)"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <E11ZHMN-0002mM-00@xxxxxxxxxxxxxxxxxx>
Zefram <zefram@xxxxxxxx> writes:
> I find it difficult to believe that anything actually relies on
> "emulate zsh" *not* resetting EXTENDED_GLOB.
This isn't really on the same subject, but a colleague wanted to
delete files beginning .# in a directory a few days ago (they're
created by Emacs ediffing files with versions or something), and did:
rm .#*
(Don't try this at home.)
I'm not sure whether this is a bug in zsh. After all, the "rm *"
warning is a special case (and useful, too, IMHO).
Hmm, how about changing the implementation of the check? Presumably
the current test looks for * explicitly; an alternative (slightly more
expensive) would be to do the expansion and see if it includes all of
the files or not, and if it does, issue the warning.
In fact, one could probably do this as a shell function, instead.
That probably makes more sense.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author