From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Bash heredoc on FD 3
Date: Mon, 03 Dec 2018 15:43:00 -0000 [thread overview]
Message-ID: <b153a5b5-deea-c039-e93a-0555d8e2dba8@gmail.com> (raw)
In-Reply-To: <5c0427c5.1c69fb81.d71e5.c8ec@mx.google.com>
On 12/2/2018 1:43 PM, Steven Penny wrote:
> Using this file:
>
> Â Â $ cat hello.sh
> Â Â awk -f /dev/fd/3 3<<eof
> Â Â BEGIN {
> Â Â Â Â print "hello world"
> Â Â }
> Â Â eof
>
> it runs as expected with Dash:
>
> Â Â $ dash hello.sh
> Â Â hello world
>
> However it fails with Bash:
>
> Â Â $ bash hello.sh
> Â Â awk: fatal: can't open source file `/dev/fd/3' for reading (No such
> file or
> Â Â directory)
>
> I tried also with Debian and both Dash and Bash work as expected. What is
> causing Cygwin Bash to fail here?
Same for me and interestingly:
$ ls -ld /dev/fd/*
ls: cannot access '/dev/fd/3': No such file or directory
ls: cannot access '/dev/fd/31': No such file or directory
lrwxrwxrwx 1 eboyd53 eboyd53 0 Dec 3 10:39 /dev/fd/0 -> /dev/pty2
lrwxrwxrwx 1 eboyd53 eboyd53 0 Dec 3 10:39 /dev/fd/1 -> /dev/pty2
lrwxrwxrwx 1 eboyd53 eboyd53 0 Dec 3 10:39 /dev/fd/2 -> /dev/pty2
--
cyg Simple
--
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 prev parent reply other threads:[~2018-12-03 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 18:43 Steven Penny
2018-12-03 15:43 ` cyg Simple [this message]
2018-12-03 15:56 ` cyg Simple
2018-12-03 17:28 ` Eliot Moss
2018-12-04 12:13 ` Houder
2018-12-04 14:22 ` cyg Simple
2018-12-05 6:55 ` Houder
2019-01-06 20:18 ` Corinna Vinschen
2019-01-07 18:28 ` Steven Penny
2019-01-07 19:03 ` Corinna Vinschen
2019-01-08 0:19 ` Steven Penny
2019-01-08 11:27 ` Corinna Vinschen
2019-01-08 21:05 ` Corinna Vinschen
2019-01-09 0:17 ` Steven Penny
2019-01-09 9:48 ` Corinna Vinschen
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=b153a5b5-deea-c039-e93a-0555d8e2dba8@gmail.com \
--to=cygsimple@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).