zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug: reading from tty inside process substitution
Date: Sun, 12 Nov 2023 13:50:58 -0800	[thread overview]
Message-ID: <CAH+w=7YhKay_8PuWn+JaJAbfVtQb_-HU8=m71Z_w6wOw=rQknw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZztRXt7R9fDK=yb1=fcvjwjiUGo98j73BgBG7NzWE+iw@mail.gmail.com>

On Sun, Nov 12, 2023 at 10:09 AM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> I doubt there's any easy way to change this without breaking something else.

This is even worse:

read foo < <(read bar; echo $bar) </dev/tty

With MULTIOS, that command becomes un-killable, because "read foo"
sees a pipeline consisting of a catenation of both the process
substitution and the tty, but the process substitution is perpetually
TTIN'd and the interactive shell is ignoring interrupts.  Without
MULTIOS, the command substitution simply becomes a stopped zombie and
"read foo" sees only /dev/tty.  Without the </dev/tty, it gets stuck
but interrupt is possible, leaving behind a zombie.


  reply	other threads:[~2023-11-12 21:51 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 [this message]
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=7YhKay_8PuWn+JaJAbfVtQb_-HU8=m71Z_w6wOw=rQknw@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).