From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug: reading from tty inside process substitution
Date: Wed, 15 Nov 2023 20:58:28 -0800 [thread overview]
Message-ID: <CAH+w=7Z0g804j+Pg1Q5O6dYpuDOYBdWcLAqSjV5u3SSd8hE_YA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y6Tm=Ri4xTR_m4cEy3Sp+Be1Nx0B62Tj2mD8L8ObHtzQ@mail.gmail.com>
I've committed the patch so far, but another case occurred to me.
On Tue, Nov 14, 2023 at 9:00 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> > On Tue, Nov 14, 2023 at 7:33 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> > >
> > > > read foo < <(read bar; echo $bar) </dev/tty
>
> ... the multio loop is still reading /dev/tty and won't discover
> until its I/O buffers fill up that "read foo" isn't consuming any more
> input.
Replace /dev/tty with /dev/zero and we're back to the unkillable loop.
It's been this way since workers/12222 in July 2000. The bug report
to which that was a response had to do with a write loop (emulating
"tee" to multiple outputs). Do we actually need to discard EINTR on
the read loop, or did that just get put in for symmetry?
next prev parent reply other threads:[~2023-11-16 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 15:59 Mark J. Reed
2023-11-12 18:09 ` Bart Schaefer
2023-11-12 21:50 ` Bart Schaefer
2023-11-15 3:33 ` Bart Schaefer
2023-11-15 4:42 ` Bart Schaefer
2023-11-15 5:00 ` Bart Schaefer
2023-11-16 4:58 ` Bart Schaefer [this message]
2023-11-17 1:27 ` [PATCH] reading from large or "infinite" source in multio Bart Schaefer
2023-11-18 23:24 ` Bart Schaefer
2023-11-16 2:35 ` [PATCH] reading from tty inside process substitution Bart Schaefer
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='CAH+w=7Z0g804j+Pg1Q5O6dYpuDOYBdWcLAqSjV5u3SSd8hE_YA@mail.gmail.com' \
--to=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).