zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: zsh-workers@zsh.org
Subject: Re: [BUG] builtin echo doesn't check write error
Date: Wed, 9 Jun 2021 16:40:50 +0100	[thread overview]
Message-ID: <20210609154050.fwnzosv2qecno3kb@chazelas.org> (raw)
In-Reply-To: <20210609153319.7h5v27vlahutfvpe@chazelas.org>

2021-06-09 16:33:19 +0100, Stephane Chazelas:
> 2021-06-09 16:17:30 +0200, Vincent Lefevre:
> > On 2021-06-09 16:09:40 +0200, Vincent Lefevre wrote:
> > > With zsh 5.8, the builtin echo doesn't check write error.
> > 
> > And that's also the case for "print", "printf" and maybe others.
> [...]
> 
> It looks as if EBADF is treated specially on purpose.
[...]

See: https://www.zsh.org/mla/workers/2002/msg00158.html

A04redirect.ztst still has:

  print foo >&-
0:'>&-' redirection

  (exec >&-
  print foo)
0:'>&-' with attempt to use closed fd
*?\(eval\):2: write error:*

That is "print" with stdout explicitely closed meant to return
success and report no error message, but "print foo" without
explicit closing outputs an error (but exit status still 0).

So it seems to work as intended, though I'm not sure what the
rationale is for that intended behaviour.

-- 
Stephane


  reply	other threads:[~2021-06-09 15:41 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 [this message]
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
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=20210609154050.fwnzosv2qecno3kb@chazelas.org \
    --to=stephane@chazelas.org \
    --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).