From: Brian Harvell <harvell@aol.net>
To: <zsh-workers@sunsite.auc.dk>
Subject: status codes on Dec OSF
Date: Thu, 21 Jun 2001 17:46:15 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.33.0106211734450.4860-100000@boondoggle.office.aol.com> (raw)
In-Reply-To: <1000304181244.ZM24879@candle.brasslantern.com>
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.
%cat foo
FOO=`jfkljfs`
echo $?
FOO=`pwd`
echo $?
jfkljfs
echo $?
pwd
echo $?
>From the dec 4.0F machine
% /opt/bcs/packages/zsh-4.0.1/bin/zsh -x foo
+foo:1> FOO=+foo:1> jfkljfs
foo:1: command not found: jfkljfs
+foo:1> FOO=
+foo:2> echo 0
0
+foo:3> FOO=+foo:3> pwd
+foo:3> FOO=/usr/users/harvell/zsh-4.0.1
+foo:4> echo 0
0
+foo:6> jfkljfs
foo:6: command not found: jfkljfs
+foo:7> echo 1
1
+foo:8> pwd
/usr/users/harvell/zsh-4.0.1
+foo:9> echo 0
0
>From the solaris 2.7 machine
% /opt/bcs/packages/zsh-4.0.1/bin/zsh -x foo
+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=/data/cvs/bcs/SOURCES/zsh-4.0.1
+foo:4> echo 0
0
+foo:6> jfkljfs
foo:6: command not found: jfkljfs
+foo:7> echo 1
1
+foo:8> pwd
/data/cvs/web-inf/bcs/SOURCES/zsh-4.0.1
+foo:9> echo 0
0
--
Brian Harvell harvell@aol.net http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next parent reply other threads:[~2001-06-21 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1000304181244.ZM24879@candle.brasslantern.com>
2001-06-21 21:46 ` Brian Harvell [this message]
2001-06-22 6:01 ` Andrej Borsenkow
2001-06-23 3:49 ` PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF) Bart Schaefer
2001-06-23 18:22 ` Bart Schaefer
2001-06-25 5:57 ` Andrej Borsenkow
2001-06-27 7:15 ` Andrej Borsenkow
2001-06-27 7:46 ` Bart Schaefer
2001-06-27 13:02 ` Brian Harvell
2001-06-22 7:03 ` status codes on Dec OSF Sven Wischnowsky
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=Pine.GSO.4.33.0106211734450.4860-100000@boondoggle.office.aol.com \
--to=harvell@aol.net \
--cc=zsh-workers@sunsite.auc.dk \
/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).