From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Bash heredoc on FD 3
Date: Tue, 08 Jan 2019 00:19:00 -0000 [thread overview]
Message-ID: <5c33ec76.1c69fb81.10fee.7eef@mx.google.com> (raw)
In-Reply-To: <20190107190313.GD593@calimero.vinschen.de>
On Mon, 7 Jan 2019 20:03:13, Corinna Vinschen wrote:
> I can't reproduce this with my latest code. It works fine for me
> every time, independently of POSIXLY_CORRECT.
>
> I uploaded new snapshots to https://cygwin.com/snapshots/ with all
> the latest changes. Please try again.
I retested with cygwin1-20190107.dll.xz. My results below. Note that "success"
means that with Bash, the script runs without error, regardless of
"POSIXLY_CORRECT" variable as you said. "failure" is to mean that with Bash,
running with "POSIXLY_CORRECT" produces this error:
awk: error: can't open source file `/dev/fd/3' for reading (Permission
denied)
Windows 10: success
Windows 8.1: failure
Windows 7: failure
Testing done using virtual machines from here:
https://developer.microsoft.com/microsoft-edge/tools/vms
Even if we must leave things as is, maybe its not that bad. Ideally it should be
working regardless of the variable as you said, but on all 3 Windows version.
But at least we have a workaround if need be. I would like to avoid unsetting
POSIXLY_CORRECT if I can though as it tends to be a net positive for me - as it
forces me to be more strict with code writing.
Also some might have the opinion "so what", lul those are old. Well, yes they
are but Windows 7 still has a higher marketshare than Windows 10:
https://netmarketshare.com/operating-system-market-share?id=platformsDesktopVersions
so until that changes I think we should consider it in the decsion making
process.
--
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:[~2019-01-08 0:19 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
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 [this message]
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=5c33ec76.1c69fb81.10fee.7eef@mx.google.com \
--to=svnpenn@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).