From: Petros Aggelatos <petrosagg@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: bug with named pipes and process substitution
Date: Wed, 22 Jul 2015 17:32:05 -0700 [thread overview]
Message-ID: <CAA+L57Un9gAxAoe+6Bd-2oXu0KLXxofMu_nJw7yLgYauAgmnvQ@mail.gmail.com> (raw)
In-Reply-To: <20150722105829.43856c6d@pwslap01u.europe.root.pri>
Hi,
Thanks a lot for the quick resolution, I tested the patch and it works
for me too. However, the test added works fine even on the master
branch without the patch (I included the mkpipe -> mkfifo change). Not
sure if I'm doing something wrong but I'm sending the test I used to
find the broken commit in case there is a problem with the current
test:
diff --git a/Test/D03procsubst.ztst b/Test/D03procsubst.ztst
index 7b87589..757ac49 100644
--- a/Test/D03procsubst.ztst
+++ b/Test/D03procsubst.ztst
@@ -126,3 +126,15 @@
eval 'foo here is some output)'
0:full alias expanded when substitution starts in alias
>here is some output
+
+ if ! (mkfifo test_pipe >/dev/null 2>&1); then
+ ZTST_skip="mkfifo not available"
+ else
+ echo 1 | tee >(cat > test_pipe) | cat - test_pipe > /dev/null &
+ sleep 1
+ if [ ! -d /proc/$! ]; then
+ echo success
+ fi
+ fi
+0:proc subst fd in forked subshell closed in parent
+>success
next prev parent reply other threads:[~2015-07-23 0:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 0:25 Petros Aggelatos
2015-07-22 9:09 ` Peter Stephenson
2015-07-22 9:58 ` Peter Stephenson
2015-07-22 10:27 ` Peter Stephenson
2015-07-22 14:45 ` Bart Schaefer
2015-07-23 1:03 ` Mikael Magnusson
2015-07-23 1:46 ` Bart Schaefer
2015-07-23 8:15 ` ChangeLog (was Re: bug with named pipes and process substitution) Kamil Dudka
2015-07-23 22:01 ` Daniel Shahaf
2015-07-23 0:32 ` Petros Aggelatos [this message]
2015-07-23 9:01 ` bug with named pipes and process substitution Peter Stephenson
2015-07-27 12:25 ` Jun T.
2015-08-08 11:59 ` m0viefreak
2015-08-08 15:21 ` Jun T.
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=CAA+L57Un9gAxAoe+6Bd-2oXu0KLXxofMu_nJw7yLgYauAgmnvQ@mail.gmail.com \
--to=petrosagg@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).