Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh: no matches found
- X-seq: zsh-users 8618
- From: Toshiro <toshiro@xxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: zsh: no matches found
- Date: Sun, 20 Mar 2005 23:04:44 -0200
- In-reply-to: <20050321004759.GC5243@xxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <200503202238.31745.toshiro@xxxxxxxxxxxxxxx> <20050321004759.GC5243@xxxxxxxxxxxxxxxx>
> In the last episode (Mar 20), Toshiro said:
> > Every time I type something like 'find . -name *log' I get the error:
> > zsh: no matches found
> > when there's no file matching the wildcard in the current directory.
> > Is there any way to change this behaviour? (I don't want to escape every
> > asterisk I type).
>
> alias find="noglob find"
>
> will work in this case. You don't want to do it globally, though,
> since almost all commands expect the shell to expand wildcards for
> them.
Is this the only way? In other shells this is implemented in a very simple
way, if the wildcard can be expanded, then it is expanded, otherwise an
asterisk is sent as an argument to the application.
Why is it so complex in zsh? What are the advantages of this implementation?
Toshiro.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author