From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: bash pipe fails in script with subshell/loop cmbination
Date: Tue, 08 Aug 2017 14:59:00 -0000 [thread overview]
Message-ID: <BN6PR2001MB10747BD7EA45331BA2FB65BCF18A0@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)
In-Reply-To: <fc3c9ce9-1e6b-485e-0a21-4d2da48f1dcc@cs.umass.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 827 bytes --]
> From: Eliot Moss
> It also works for me. If it is not a version issue, then I
> wonder about BLODA. Maybe anti-virus or similar tools are
> wrapping process creation in such a way that things get
> confused. Try cygcheck, etc.
BTW, it also works for me.
With so many Cygwin issues being attributed to BLODA, I wonder
if there is a reasonably small set of things that BLODA breaks
that could be tested in code, and that such a bloda-checking
program could be added to the package repertoire? (Of course,
SHTDI and, sadly, such a task is not in my skill set.)
--Ken Nellis
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2017-08-08 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 14:20 Ronald Fischer
2017-08-08 14:29 ` Eliot Moss
2017-08-08 14:59 ` Nellis, Kenneth [this message]
2017-08-08 19:41 ` cyg Simple
-- strict thread matches above, loose matches on Subject: below --
2017-08-08 13:59 Wouter van Doorn
2017-08-08 14:20 ` Ronald Otto Valentin Fischer
2017-08-08 16:37 ` Achim Gratz
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=BN6PR2001MB10747BD7EA45331BA2FB65BCF18A0@BN6PR2001MB1074.namprd20.prod.outlook.com \
--to=kenneth.nellis@conduent.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).