Re: run.exe 1.1.10: Does not hide cmd window under Windows 7 x64

2011-07-20 Thread Charles Wilson
On 7/20/2011 4:30 PM, Larry Hall (Cygwin) wrote: > FWIW, your recipe works the way you want with 1.1.13-1 on my > W7 x64 box. Yes, the OP needs to upgrade to 1.1.13 (well, at least 1.1.11): -- run-1.1.11-1 - 2009-08-10 --- * Added patch to support invisible consoles on Windows 7

Re: ioctl: FIONREAD and ENOTTY

2011-07-20 Thread Yaakov (Cygwin/X)
On Wed, 2011-07-20 at 17:46 +0200, Corinna Vinschen wrote: > On Jul 20 03:11, Yaakov (Cygwin/X) wrote: > > On Linux, ioctl(2) returns several different errors[1]: > > > > EBADF d is not a valid descriptor. > > EFAULT argp references an inaccessible memory area. > > EINVAL Request or argp is not v

Re: run.exe 1.1.10: Does not hide cmd window under Windows 7 x64

2011-07-20 Thread Larry Hall (Cygwin)
On 7/20/2011 4:10 PM, Garrett Cooper wrote: Summary: run.exe 1.1.10 does not hide cmd window under Windows 7 x64. Details: Prior to a recent upgrade to Windows 7 x64 I have been using run.exe to launch svn+ssh commands in Tortoise SVN for years. After the upgrade I installed cygwin including

run.exe 1.1.10: Does not hide cmd window under Windows 7 x64

2011-07-20 Thread Garrett Cooper
Summary: run.exe 1.1.10 does not hide cmd window under Windows 7 x64. Details: Prior to a recent upgrade to Windows 7 x64 I have been using run.exe to launch svn+ssh commands in Tortoise SVN for years.  After the upgrade I installed cygwin including openssh and run.exe and noticed that all comma

Re: [ -w filename ] returns true when permissions are -r--r--r--

2011-07-20 Thread Eric Blake
On 07/20/2011 12:05 PM, Reid Thompson wrote: Is this broken? Or a known windows/cygwin discrepancy? Or am I missing something with my posix/windows file permissions settings If you are running as an administrator, that might explain it. Admins can alter any file regardless of permissions, i

Re: [ -w filename ] returns true when permissions are -r--r--r--

2011-07-20 Thread Larry Hall (Cygwin)
On 7/20/2011 2:07 PM, Reid Thompson wrote: On Wed, 2011-07-20 at 14:05 -0400, Reid Thompson wrote: Is this broken? Or a known windows/cygwin discrepancy? Or am I missing something with my posix/windows file permissions settings reid.thompson@ws-jrt ~ $ ls -rlt afile -r--r--r-- 1 reid.thompson

Re: [ -w filename ] returns true when permissions are -r--r--r--

2011-07-20 Thread Reid Thompson
On Wed, 2011-07-20 at 14:05 -0400, Reid Thompson wrote: > Is this broken? Or a known windows/cygwin discrepancy? Or am I missing > something with my posix/windows file permissions settings > > reid.thompson@ws-jrt ~ > $ ls -rlt afile > -r--r--r-- 1 reid.thompson Domain Users 6 2011-07-20 14:02 a

[ -w filename ] returns true when permissions are -r--r--r--

2011-07-20 Thread Reid Thompson
Is this broken? Or a known windows/cygwin discrepancy? Or am I missing something with my posix/windows file permissions settings reid.thompson@ws-jrt ~ $ ls -rlt afile -r--r--r-- 1 reid.thompson Domain Users 6 2011-07-20 14:02 afile reid.thompson@ws-jrt ~ $ if [ -w afile ]; then echo " file i

Re: 'info ftp' show man page instead of info. Incorrect 'dir' file entries for 'inetutils' package.

2011-07-20 Thread Charles Wilson
On 7/14/2011 4:56 AM, Oleksandr Gavenko wrote: > Problems come from incorrect '/usr/share/info/dir' file menu entry. > If I change: > > * ftp: (inetutils)ftp FTP client. > > to: > > * ftp: (inetutils)ftp invocation. FTP client. > > - all OK. Same true for many othe

Re: ioctl: FIONREAD and ENOTTY

2011-07-20 Thread Corinna Vinschen
On Jul 20 03:11, Yaakov (Cygwin/X) wrote: > On Linux, ioctl(2) returns several different errors[1]: > > EBADF d is not a valid descriptor. > EFAULT argp references an inaccessible memory area. > EINVAL Request or argp is not valid. > ENOTTY d is not associated with a character special device. > E

Re: Error when Perl calling shell scipt using Cygwin >>> c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487

2011-07-20 Thread Gaurav Chhabra
2011/7/15 Gaurav Chhabra: > Sorry, i forgot mentioning that i have attached the log files > (perlrebase and main error that i am getting) for reference in my > last post. >> The perlrebase log looks good, but the other log indicates that you need to do a rebaseall. http://old.nabble.com/file/p32

Re: [bash or DLL] Memory leak in childs

2011-07-20 Thread Luiz Claudio Valdetaro
Classic this is windows for you. And they want me to get a phone based in Windows? Or a Ford Fusion, based on Windows? LOL On 7/19/2011 8:40 PM, Mark Geisert wrote: Heiko Elger writes: I just used another small testcase doing the same. [...] $ cat test2.sh #!/bin/sh trap "echo TRAP; exit

Re: Can't start graphic menu in remote machine

2011-07-20 Thread Ciro
Hi Dima, I'm running Cygwin/X, yes, I can run xterm or rxvt locally, in fact I could run the graphic interface in the remote server until I installed the new Cygwin/X. I'm not sur ewhat the problem could be. Dima Pasechnik-2 wrote: > > On 19 July 2011 14:05, Ciro wrote: >> >> Hi, >> >> I've

Re: New GCC? (Was: Re: Vim segv'ing)

2011-07-20 Thread Chris Sutcliffe
On 1 July 2011 19:00, Chris Sutcliffe wrote: > On 1 July 2011 15:36, Chris Sutcliffe wrote: >> I know Yaakov has asked a few times now, it would really be nice to >> have a 4.5.x release of the native Cygwin compiler.  I'm curious if >> the issues I'm having with the latest rtorrent / libtorrent re

ioctl: FIONREAD and ENOTTY

2011-07-20 Thread Yaakov (Cygwin/X)
On Linux, ioctl(2) returns several different errors[1]: EBADF d is not a valid descriptor. EFAULT argp references an inaccessible memory area. EINVAL Request or argp is not valid. ENOTTY d is not associated with a character special device. ENOTTY The specified request does not apply to the kind o

Re: [bash or DLL] Memory leak in childs

2011-07-20 Thread Corinna Vinschen
On Jul 20 04:54, Heiko Elger wrote: > Mark Geisert writes: > > > > int main(int argc, char** argv[]) > > > > (I won't point out the error in the above line.) > Oops ... > > > The good news is that I was then able to reproduce the issue without Cygwin. > OK - I was able to reproduce the issue to