Re: Redirecting stderr to stdout through pipe doesn't work the way it does in Linux
- Date: Wed, 5 Dec 2018 14:43:33 -0500
- From: cyg Simple <cygsimple@xxxxxxxxx>
- Subject: Re: Redirecting stderr to stdout through pipe doesn't work the way it does in Linux
On 12/5/2018 1:33 PM, David Karr wrote:
On Wed, Dec 5, 2018 at 9:43 AM cyg Simple <cygsimple@xxxxxxxxx> wrote:
Your query got me interested in looking and I believe that winpty needs
to be at the front of all the commands so that it can communicate with
mintty properly. To overcome the need to remember you could add an
alias to execute the command; `alias FOO="winpty FOO"'.
Sigh. What a mess. I can't get this to work. It was easy enough when a
single script has to execute "kubectl", having "winpty" prefix that call,
but I'm trying to write a script that calls that other script, and even in
If I have "winpty" prefix the call to the script that calls "kubectl", it
winpty: error: cannot start '...': Not found in PATH
When I changed it so it references the absolute path, it then says "%1 is
not a valid Win32 application. (error 0xc1)". So, this makes it clear that
winpty can only directly execute Windows applications, which makes sense.
So how can I call a Windows application from more than just the top-level
What does cygcheck say about your winpty? You are using the Cygwin
compiled version, correct?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple