X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 4 Apr 2012 10:00:37 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe
Message-ID:	<20120404080037.GX8014@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20120403055503 DOT GA6387 AT raf DOT org> <4F7AD7F3 DOT 4030208 AT cs DOT umass DOT edu> <20120404003419 DOT GA16890 AT raf DOT org> <4F7B9F99 DOT 4030508 AT cs DOT umass DOT edu> <20120404034204 DOT GA18871 AT raf DOT org>
MIME-Version:	1.0
In-Reply-To:	<20120404034204.GA18871@raf.org>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Apr  4 13:42, raf wrote:
> Eliot Moss wrote:
> 
> > On 4/3/2012 8:34 PM, raf wrote:
> > >Eliot Moss wrote:
> > >
> > >>My suggestion would be to read up on the cygpath utility
> > >>program and use it to convert cygwin paths to ones suitable
> > >>for a non-cygwin program, etc.  I launch non-cygwin programs
> > >>all the time on Windows 7 that way ...
> > >>
> > >>Regards -- Eliot Moss
> > >
> > >Hi,
> > >
> > >Thanks but I'm using a non-cygwin path already.
> > >I am not using a cygwin path that needs to be
> > >converted to anything.
> > 
> > Except you wrote F:/blah which is *not* a Windows
> > path.  F:\blah is ...
> 
> Never mind. The problem has nothing to do with the command
> line arguments or path flavours.
> 
> I think it has more to do with the change in terminal handling.
> The password prompting is no longer working (even in mintty).
> The lack of debug output was just buffering.

The problem is that native Windows CLI applications usually don't
work interactively with Cygwin's pseudo ttys as stdio descriptors.

> The users can run the programme from cmd.exe so I'll set up
> some .bat scripts for them instead of bash functions if I
> can't easily get it working from within cygwin.

You can use the still existing Cygwin.bat script from Cygwin's root
directory to start a Cygwin bash in a Windows console window.  The
password prompting will still work there.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

- Raw text -