zsh-workers
 help / color / mirror / code / Atom feed
From: <zeurkous@volny.cz>
To: <zsh-workers@zsh.org>
Subject: patch: zshmisc(1) clarify non-successful exit statuses
Date: Sun, 11 Apr 2021 14:15:20 +0200	[thread overview]
Message-ID: <20210411141520.4ABA89D5@volny.cz> (raw)

#?patch
#
# These patches add, to the zshmisc(1) manual page, clarity about the
# exit status on exec failure.
#
# Me understands that, strictly considered, only Doc/Zsh/exec.yo needs
# updating; however, as me doesn't have yodl, me updated Doc/zshmisc.1
# as well.
#
# Hope this is useful (it is to me),
#
#         --zeurkous, Sun Apr 11 11:12:21 UTC 2021.
#
--- Doc/Zsh/..v/5.8/exec.yo	Mon Dec  4 14:09:35 2017
+++ Doc/Zsh/exec.yo	Sun Apr 11 10:42:15 2021
@@ -16,7 +16,10 @@
 Otherwise, the shell searches each element of tt($path) for a
 directory containing an executable file by that name.  If the
 search is unsuccessful, the shell prints an error message and returns
-a nonzero exit status.
+127.
+
+If execution fails because of insufficient permissions, or because the
+file is a directory, the shell prints an error message and returns 126.
 
 If execution fails because the file is not in executable format,
 and the file is not a directory, it is assumed to be a shell

--- Doc/..v/5.8/zshmisc.1	Fri Feb 14 22:13:03 2020
+++ Doc/zshmisc.1	Sun Apr 11 10:55:17 2021
@@ -1,4 +1,4 @@
-.TH "ZSHMISC" "1" "February 14, 2020" "zsh 5\&.8"
+.TH "ZSHMISC" "1" "April 11, 2021" "zsh 5\&.8"
 .SH "NAME"
 zshmisc \- everything and then some
 .\" Yodl file: Zsh/grammar.yo
@@ -1171,7 +1171,10 @@
 Otherwise, the shell searches each element of \fB$path\fP for a
 directory containing an executable file by that name\&.  If the
 search is unsuccessful, the shell prints an error message and returns
-a nonzero exit status\&.
+127\&.
+.PP
+If execution fails because of insufficient permissions, or because the
+file is a directory, the shell prints an error message and returns 126\&.
 .PP
 If execution fails because the file is not in executable format,
 and the file is not a directory, it is assumed to be a shell


             reply	other threads:[~2021-04-11 12:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 12:15 zeurkous [this message]
2021-04-13 15:52 ` Daniel Shahaf
2021-04-13 18:03   ` zeurkous
2021-04-14 11:03     ` Daniel Shahaf
2021-04-14 11:40       ` zeurkous
2021-04-23 12:18         ` revised " zeurkous
2021-04-23 16:07           ` Daniel Shahaf
2021-04-23 16:15             ` Daniel Shahaf
2021-04-23 20:25             ` zeurkous
2021-04-23 20:14           ` Lawrence Velázquez
2021-04-23 20:29             ` zeurkous
2021-04-23 20:39               ` Lawrence Velázquez
2021-04-23 20:57                 ` zeurkous
2021-04-23 20:51           ` Bart Schaefer
2021-04-23 21:03             ` zeurkous
2021-04-23 21:12               ` Bart Schaefer
2021-04-23 21:18                 ` zeurkous
2021-04-23 22:31                   ` Bart Schaefer
2021-04-26 16:25             ` zeurkous
2021-04-29 14:20               ` Daniel Shahaf
2021-05-09 19:04                 ` Lawrence Velázquez
2021-05-31  1:09                   ` Lawrence Velázquez
2021-05-31  4:09                     ` Bart Schaefer
2021-05-31  4:37                       ` Lawrence Velázquez
2021-06-30 17:51                     ` zeurkous
2021-06-30 22:12                       ` Lawrence Velázquez

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=20210411141520.4ABA89D5@volny.cz \
    --to=zeurkous@volny.cz \
    --cc=zsh-workers@zsh.org \
    /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).