X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 24 Mar 2009 11:17:15 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.7.0: Getting a Windows app to run synchronously to a script from which it is invoked Message-ID: <20090324101715.GC9322@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <49C6D72D DOT 4090804 AT veritech DOT com> <20090323092845 DOT GJ9322 AT calimero DOT vinschen DOT de> <49C822E9 DOT 2050603 AT veritech DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49C822E9.2050603@veritech.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 23 20:01, Lee D. Rothstein wrote: > Corinna Vinschen wrote: >> On Mar 22 20:26, Lee D.Rothstein wrote: >> >> > >> First of all, the explorer command does not stop input from the >> terminal. When I invoke the above script, I get an explorer window >> *and* I can type into the calling shell again because explorer is >> running detached. Experiments with notepad show that notepad is running >> synchronously, so in that case the shell is waiting for notepad to exit. >> I get this behaviour consistently on 1.5 and 1.7. >> > This is my oversight. I used the wrong example, but even for the right > example, I believe I > misdiagnosed the problem. The correct, verified diagnosis follows (I hope). > > After some more research I find the actual problem with Cygwin 1.7, is that > if you try to open open a file with a Windows app through its softlink, > (in the > directory of both the file and its softlink) the Windows app opens the > softlink, not the file to which it is linked. This only happens with > Windows apps, and > the problem does not happen with Cygwin 1.5. (I just tested it on both > versions.) Hmm. What kind of "softlink" are you talking about? Is that a Windows shortcut created by Windows? Or is that a Cygwin symlink? If the latter, did you create the symlink way back when, or did you create the symlink under Cygwin 1.7? If the latter, the symlink is probably not a Windows shortcut anymore, rather the other Cygwin style of symlink which is a file with the SYSTEM DOS attribute set. In this case it's no wonder Windows opens the file, rather than to follow the shortcut to its target. I made the change because the SYSTEM type shortcuts are faster. If you want to have the Windows shortcut style symlinks back because you use them to interoperate with native Windows tools, you have to set the CYGWIN=winsymlinks option now. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/