From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Cc: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: [BUG] builtin echo doesn't check write error
Date: Thu, 10 Jun 2021 10:11:52 +0200 [thread overview]
Message-ID: <20210610081152.GA897070@zira.vinc17.org> (raw)
In-Reply-To: <20210609181617.k5jbq3z37lt7ry5s@chazelas.org>
On 2021-06-09 19:16:17 +0100, Stephane Chazelas wrote:
> 2011 workers/29845 Peter notices the error is displayed in
> (exec >&-; print) and adds a test case for it, but I'm not
> sure he correctly identified why.
I also find this disturbing:
zira% (exec >&-; echo)
zsh: write error: bad file descriptor
zira% (exec >&-; echo >&-)
zira%
(or with "print" instad of "echo").
> POSIX does say that printf/echo should return with a non-zero
> exit status upon error, and stderr be used for diagnostix
> errors as usual. It's not clear to me if implementations are at
> liberty to decide whether a write() error is considered an error
> or not.
Well, in almost all cases, e.g. when the close is not in the same
command, and when this is not fd 1 (stdout), but other fd, such as
in "echo foo 3>&- >&3", one gets an error. So this is already very
inconsistent.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2021-06-10 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:09 Vincent Lefevre
2021-06-09 14:17 ` Vincent Lefevre
2021-06-09 15:33 ` Stephane Chazelas
2021-06-09 15:40 ` Stephane Chazelas
2021-06-09 15:59 ` Stephane Chazelas
2021-06-09 16:13 ` Bart Schaefer
2021-06-09 18:16 ` Stephane Chazelas
2021-06-10 8:11 ` Vincent Lefevre [this message]
2021-06-24 8:47 ` Vincent Lefevre
2021-06-24 9:07 ` Vincent Lefevre
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=20210610081152.GA897070@zira.vinc17.org \
--to=vincent@vinc17.net \
--cc=schaefer@brasslantern.com \
--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).