Mail Archives: cygwin/2009/03/22/19:26:31
This is in all probability, not a bug. I suspect it falls into CGF's
category of "works but isn't (wasn't) guaranteed."
All of my scripts (developed under Cygwin 1.5 or earlier) that involve
a Windows native app use:
winapp "$(cygpath -w $something)"
have stopped working "properly" since I installed Cygwin 1.7.
Here's the script I use, FOR EXAMPLE, for invoking Windows Explorer to the
current directory or a specified Cygwin directory path, AND that stops
further use of the invoked from "terminal" window, until this Explorer
window terminates:
#!/usr/bin/bash
if [[ -n "$1" ]] ; then cd "$1" ; fi
explorer "$(cygpath -w .)"
Explorer opens okay, but always to the "Computer" folder, rather than the
current working or specified directory. (Yes, I know that there is a
special option for Explorer in 'cygstart'. Please read on.)
I found that I can make the above work by replacing the invocation using
'cygpath' with a 'cygstart' initiated invocation without 'cygpath', at
all. The problem with this latter fix, however, is that 'cygstart' invokes
the Windows app asynchronously to the script in which it is contained.
Sometimes I want the script continuance to be "tethered" to the Windows
app, and the only way to do this (that I can see), is to put an otherwise
superfluous 'read' statement right after the Windows app invocation. Ugly,
and not as obvious, to the user, as the old method.
Is there no straight-forward way to invoke a windows app from a script
synchronously with Cygwin 1.7?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -