From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19123 invoked from network); 22 Jun 2001 07:05:34 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 22 Jun 2001 07:05:34 -0000 Received: (qmail 26769 invoked by alias); 22 Jun 2001 07:04:43 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15039 Received: (qmail 26755 invoked from network); 22 Jun 2001 07:04:42 -0000 From: Sven Wischnowsky Date: Fri, 22 Jun 2001 09:03:32 +0200 (MET DST) Message-Id: <200106220703.JAA15822@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.dk Subject: Re: status codes on Dec OSF In-Reply-To: Brian Harvell wrote: > The following script produces different results when run on a dec machine vs > a solaris machine. It seems the dec doesn't see the status code of the command > if your setting the output to a varible. Hrm. I have a DEC Alpha with OSF 4.0f, too, but it works for me (with the current cvs version, but I don't think any of the recent changes would have any effect on this): +foo:1> FOO=+foo:1> jfkljfs foo:1: command not found: jfkljfs +foo:1> FOO= +foo:2> echo 1 1 +foo:3> FOO=+foo:3> pwd +foo:3> FOO=/home/wischnow/zsh/z/Src/ff +foo:4> echo 0 0 +foo:6> jfkljfs foo:6: command not found: jfkljfs +foo:7> echo 1 1 +foo:8> pwd /home/wischnow/zsh/z/Src/ff +foo:9> echo 0 0 Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de