Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe (really tty issue?)

2012-04-09 Thread raf
Corinna Vinschen wrote: > On Apr 6 10:27, raf wrote: > > Corinna Vinschen wrote: > > > > > On Apr 4 13:42, raf wrote: > > > > 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 wa

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe (really tty issue?)

2012-04-06 Thread Corinna Vinschen
On Apr 6 10:27, raf wrote: > Corinna Vinschen wrote: > > > On Apr 4 13:42, raf wrote: > > > 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

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe (really tty issue?)

2012-04-05 Thread raf
Corinna Vinschen wrote: > On Apr 4 13:42, raf wrote: > > 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 usua

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-04 Thread Eliot Moss
On 4/4/2012 7:54 AM, Earnie Boyd wrote: On Tue, Apr 3, 2012 at 9:10 PM, Eliot Moss wrote: Except you wrote F:/blah which is *not* a Windows Sorry to call you out on this but you're spreading misinformation. F:/blah is as much a Windows path as is F:\blah is. Open you cmd.exe and type ``dir F:

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-04 Thread Earnie Boyd
On Tue, Apr 3, 2012 at 9:10 PM, Eliot Moss wrote: > Except you wrote F:/blah which is *not* a Windows Sorry to call you out on this but you're spreading misinformation. F:/blah is as much a Windows path as is F:\blah is. Open you cmd.exe and type ``dir F:/blah'' to see that I'm correct. It is on

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-04 Thread Corinna Vinschen
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-cyg

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-03 Thread Warren Young
On 4/3/2012 7:10 PM, Eliot Moss wrote: Except you wrote F:/blah which is *not* a Windows path. F:\blah is ... Actually, forward slashes are legal path separators in Windows, and have been going back to the earliest days of MS-DOS: http://goo.gl/rm1EJ This is why you can't create a file or f

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-03 Thread raf
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 t

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-03 Thread Eliot Moss
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,

Re: Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe

2012-04-03 Thread Earnie Boyd
On Tue, Apr 3, 2012 at 1:55 AM, cygwin at raf.org wrote: > On the Windows XP computer, this works. On the Windows 7 > computer, after entering the command line and pressing > enter, nothing happens until we press Ctrl-C to terminate > it. Adding debug output to the very start of the programme > em