Greetings, David Karr!
> 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
> a pipeline.
> If I have "winpty" prefix the call to the script that calls "kubectl", it
> says:
> winpty: error: cannot start '...': Not found in PATH
Either
kubectl(){ .../winpty ...\\kubectl }; readonly -f kubectl
> 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
> script?
or write a Cygwin wrapper for kubectl and place it where it is usually located
on *NIX system.
Do NOT add kubectl or winpty to Cygwin $PATH, since both are not Cygwin apps
and their presence only confuses you.
Wrapper would probably be more universal.
--
With best regards,
Andrey Repin
Thursday, December 6, 2018 3:09:46
Sorry for my terrible english...
--
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
