From: Bart Schaefer <schaefer@brasslantern.com>
To: "Mark J. Reed" <markjreed@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Bug: reading from tty inside process substitution
Date: Sun, 12 Nov 2023 10:09:45 -0800 [thread overview]
Message-ID: <CAH+w=7ZztRXt7R9fDK=yb1=fcvjwjiUGo98j73BgBG7NzWE+iw@mail.gmail.com> (raw)
In-Reply-To: <CAA=-s3xCf4wx826U8jEjO_j5-1kcTi8v2=VZPiabKMo-meKq0Q@mail.gmail.com>
On Sun, Nov 12, 2023 at 7:59 AM Mark J. Reed <markjreed@gmail.com> wrote:
>
> The below code hangs after reading the line from the terminal:
>
> read foo < <(read bar </dev/tty; echo $bar)
I believe it actually hangs before reading the line from the terminal,
or more precisely at the point of trying to read the line. "read bar"
is being stopped by a SIGTTIN signal because it is not in a process
group that "owns" the TTY.
This has to do with the way zsh backgrounds the process substitution.
It actually works fine in a script or even in a subshell (which
explains why it works in command substitution):
% zsh -fc 'read foo < <(read bar </dev/tty; echo $bar); echo $foo'
the line
the line
% ( read foo < <(read bar </dev/tty; echo $bar); echo $foo )
subshell
subshell
%
In an interactive shell with job control, though, the process
management is different.
% unsetopt monitor
% read foo < <(read bar </dev/tty; echo $bar); echo $foo
no job control
no job control
%
I doubt there's any easy way to change this without breaking something else.
next prev parent reply other threads:[~2023-11-12 18:10 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 [this message]
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
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=7ZztRXt7R9fDK=yb1=fcvjwjiUGo98j73BgBG7NzWE+iw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=markjreed@gmail.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).