From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.auc.dk>
Subject: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)
Date: Sat, 23 Jun 2001 03:49:18 +0000 [thread overview]
Message-ID: <1010623034918.ZM6314@candle.brasslantern.com> (raw)
In-Reply-To: <000601c0fae0$d819c640$21c9ca95@mow.siemens.ru>
On Jun 22, 10:01am, Andrej Borsenkow wrote:
} Subject: RE: status codes on Dec OSF
}
} > >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
}
}
} Sigh, this is a bug :-(
It's a bug on a particular operating system, and one which Sven was not
able to reproduce.
I'm made suspicious by "/opt/bcs/" in the command name. That smells of
"binary compatibility standard" to me -- which could mean that zsh was
not compiled for the operating system under which it is executing.
Apparently quoting from the POSIX standard, Andrej goes on:
} If there is a command name, execution will continue as described in Command
} Search and Execution . If there is no command name, but the command
} contained a command substitution, the command will complete with the exit
} status of the last command substitution performed. Otherwise, the command
} will complete with a zero exit status.
}
} If a command is not found, the exit status will be 127. If the command name
} is found, but it is not an executable utility, the exit status will be 126.
} Applications that invoke utilities without using the shell should use these
} exit status values to report similar errors.
Zsh already conforms to the first paragraph (or at least attempts to); the
patch below deals with the second paragraph. Sample output:
zagzig% foo=`stamp-h`
zsh: command not found: stamp-h
zagzig% echo $?
127
zagzig% foo=`./stamp-h`
zsh: permission denied: ./stamp-h
zagzig% echo $?
126
zagzig% echo foo=`./stamp-h`
zsh: permission denied: ./stamp-h
foo=
zagzig% echo $?
0
Is there any possibility that anyone is relying explicitly upon (($? == 1))
as was formerly the case for both command-not-found and permission-denied?
--- zsh-forge/current/Src/exec.c Wed Jun 20 08:57:01 2001
+++ zsh-4.0/Src/exec.c Fri Jun 22 20:04:31 2001
@@ -502,7 +502,7 @@
(arg0[0] == '.' && (arg0 + 1 == s ||
(arg0[1] == '.' && arg0 + 2 == s)))) {
zerr("%e: %s", arg0, errno);
- _exit(1);
+ _exit(errno == EACCES ? 126 : 127);
}
break;
}
@@ -556,7 +556,7 @@
zerr("%e: %s", arg0, eno);
else
zerr("command not found: %s", arg0, 0);
- _exit(1);
+ _exit(eno == EACCES ? 126 : 127);
}
#define RET_IF_COM(X) { if (iscom(X)) return docopy ? dupstring(X) : arg0; }
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-06-23 3:51 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 ` status codes on Dec OSF Brian Harvell
2001-06-22 6:01 ` Andrej Borsenkow
2001-06-23 3:49 ` Bart Schaefer [this message]
2001-06-23 18:22 ` PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF) 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=1010623034918.ZM6314@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).