From: David Karr <davidmichaelkarr@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Redirecting stderr to stdout through pipe doesn't work the way it does in Linux
Date: Wed, 05 Dec 2018 14:58:00 -0000 [thread overview]
Message-ID: <CAA5t8Vq0y-TEioRa1krjZuMrYpEPz0zncpbArNsqpnGWWkHMrQ@mail.gmail.com> (raw)
In-Reply-To: <6cc83f4b-b0b1-d5c9-8d59-94c51382e4e3@gmail.com>
On Tue, Dec 4, 2018 at 12:52 PM Marco Atzeri <marco.atzeri@gmail.com> wrote:
> Am 04.12.2018 um 21:41 schrieb David Karr:
> > "CYGWIN_NT-6.1 WACDTL03DK068X 2.9.0(0.318/5/3)"
> >
> > I installed a version of "kubectl" for windows, and I use it extensively
> in
> > Cygwin bash for scripting command-line automation. In general, this works
> > perfectly fine. I even use the same scripting in a Linux VM.
> >
> > I'm seeing an issue with one script that works fine in the Linux VM, but
> > not in Cygwin.
> >
> > The command line is approximately this:
> >
> > kubectl exec pod -c container -i -t -- grep "string"
> stuff.properties
> > 2>&1 | sed -e 's/^propname=//'
> >
> > In Linux, this works perfectly fine. In Cygwin, it says "stdout is not a
> > tty".
> >
> > I haven't updated my local Cygwin installation for quite a while. I'd
> > prefer not to, unless there is a strong chance this kind of thing would
> be
> > fixed.
> >
>
> as kubectl is not a Cygwin program, it is not aware of cygwin pty.
> You can try to use winpty to overcome the problem.
>
> https://github.com/rprichard/winpty
>
>
>
>
Oh. Senior moment. I actually already knew that. In fact, I even have
another scripting element calling "exec" already using winpty. Thanks for
the reminder.
--
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-05 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 20:41 David Karr
2018-12-04 20:52 ` Marco Atzeri
2018-12-04 21:39 ` cyg Simple
2018-12-05 14:58 ` David Karr [this message]
2018-12-05 15:11 ` David Karr
2018-12-05 17:42 ` cyg Simple
2018-12-05 18:33 ` David Karr
2018-12-05 19:43 ` cyg Simple
2018-12-05 22:25 ` David Karr
2018-12-06 16:21 ` cyg Simple
2018-12-06 0:20 ` Andrey Repin
2018-12-06 1:03 ` 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=CAA5t8Vq0y-TEioRa1krjZuMrYpEPz0zncpbArNsqpnGWWkHMrQ@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).