X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Wed, 4 Apr 2012 10:00:37 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe
Message-ID: <20120404080037.GX8014@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20120403055503.GA6387@raf.org> <4F7AD7F3.4030208@cs.umass.edu> <20120404003419.GA16890@raf.org> <4F7B9F99.4030508@cs.umass.edu> <20120404034204.GA18871@raf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20120404034204.GA18871@raf.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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

