From: David Karr <davidmichaelkarr@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Piping input from subprocess loses track of temp file
Date: Fri, 19 Jul 2019 18:28:00 -0000 [thread overview]
Message-ID: <CAA5t8VpepGY+ZitXTe1fQp6vDe4dqDaM+0Kp1LGWZQTERuJ7Nw@mail.gmail.com> (raw)
I believe the relevant part of my cygwin version info is "3.0.7(0.338/5/3)"
(from uname -a output).
I'm working on a script where one step executes a process where the input
is taking from a subprocess, like this:
someprocess <(cat $outfile | sed -e "s/${property}[
]*=.*$/${property}=${newValue}/") ...
When I run this, I see:
error: error reading /dev/fd/62: The system cannot find the path
specified.
I tried running the exact same command line and script in Ubuntu 16.04, and
it works fine.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2019-07-19 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 18:28 David Karr [this message]
2019-07-27 15:40 ` Ken Brown
2019-07-29 1:30 ` David Karr
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=CAA5t8VpepGY+ZitXTe1fQp6vDe4dqDaM+0Kp1LGWZQTERuJ7Nw@mail.gmail.com \
--to=davidmichaelkarr@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).