From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27507 invoked from network); 14 Jan 2003 18:06:44 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 14 Jan 2003 18:06:44 -0000 Received: (qmail 12944 invoked by alias); 14 Jan 2003 18:06:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 18116 Received: (qmail 12921 invoked from network); 14 Jan 2003 18:06:26 -0000 Date: Tue, 14 Jan 2003 18:57:08 +0100 From: DervishD To: Peter Stephenson Cc: Zsh Subject: Re: Why this doesn't work in zsh? Message-ID: <20030114175708.GB2403@DervishD> Mail-Followup-To: Peter Stephenson , Zsh References: <20030114160434.GB1630@DervishD> <25.1042565949@csr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <25.1042565949@csr.com> User-Agent: Mutt/1.4i Organization: Pleyades User-Agent: Mutt/1.4i Hi Peter :) > > It has to work with both bash and zsh, but zsh says, when the > > assignment is done, '* not found'. > You can stick a backslash before the =; that works in bash, too, since > you can quote any character, even if it's not special. OK, then, that's the solution :)) Thanks a lot :) > The problem is that it's using path expansion `=prog', but I couldn't > tell you why it should at that point; in fact, I suspect it shouldn't. > Hence `setopt noequals' or `setopt nonomatch' would remove the problem, > if you can live with the side effects. Yes, the problem is noequals, I discovered after sending the message. I can live with side effects, of course, but the problem is that I cannot tell the script users to set appropriate options when running this on their systems. The better solution is to quote the character. Thanks a lot :))) Raśl