Re: file path resolution in DOS window vs mintty window

2014-01-25 Thread Andrey Repin
Greetings, Larry Hall (Cygwin)! >> I would like to understand why Cygwin style paths do not work in a CMD (DOS) >> window on my 32-bit Cygwin system, but work fine on my 64-bit Cygwin >> install. >> >> Here is a simple example of the issue: >> >> #include >> #include >> #include >> #include >>

Re: Windows 7 64 Bit - Mounting Network Drives

2014-01-25 Thread Andrey Repin
Greetings, Frank Redeker! >> (SNIP) >> >> $ ls -ld /?/* >> ls: cannot access /?/*: No such file or directory >> >> $ ls -ld /a/* >> drwxr-xr-x 1 AnrDaemon - 0 Jun 26 2012 /a/Android >> drwxr-xr-x 1 AnrDaemon - 0 Nov 5 10:58 /a/Info&Txt >> drwxr-xr-x 1 AnrDaemon ---

Re: Windows 7 64 Bit - Mounting Network Drives

2014-01-25 Thread Andrey Repin
Greetings, Damian Harty! >> Can you please do the following commands in order (native windows console >> preferred, but not necessary): >> net use > % net use > New connections will be remembered. > Status Local RemoteNetwork > >

Re: Maintainer for git?

2014-01-25 Thread Balaji Venkataraman
On Sat, Jan 25, 2014 at 3:59 AM, Corinna Vinschen wrote: > I have a hunch that this is not a OpenSSL but a Cygwin problem. > > The default case in OpenSSL is to use SSE2 instructions in the x86 > assembler code. However, SSE2 instructions utilize the x86 XMM > registers, which are not saved and re

Re: file path resolution in DOS window vs mintty window

2014-01-25 Thread Larry Hall (Cygwin)
On 1/25/2014 3:04 PM, Steven Bardwell wrote: I would like to understand why Cygwin style paths do not work in a CMD (DOS) window on my 32-bit Cygwin system, but work fine on my 64-bit Cygwin install. Here is a simple example of the issue: #include #include #include #include void main() {

Re: mintty shell gets frequent "8~" strings inserted into input

2014-01-25 Thread Larry Hall (Cygwin)
On 1/25/2014 5:27 PM, Larry Hall (Cygwin) wrote: On 1/24/2014 9:40 PM, KARR, DAVID wrote: -Original Message- Larry Hall (Cygwin) Sent: Friday, January 24, 2014 12:14 PM Subject: Re: mintty shell gets frequent "8~" strings inserted into input On 1/24/2014 2:57 PM, KARR, DAVID wrote: ---

Re: mintty shell gets frequent "8~" strings inserted into input

2014-01-25 Thread Larry Hall (Cygwin)
On 1/24/2014 9:40 PM, KARR, DAVID wrote: -Original Message- Larry Hall (Cygwin) Sent: Friday, January 24, 2014 12:14 PM Subject: Re: mintty shell gets frequent "8~" strings inserted into input On 1/24/2014 2:57 PM, KARR, DAVID wrote: -Original Message- Larry Hall (Cygwin) Sent:

Re: Maintainer for git?

2014-01-25 Thread David Rothenberger
On 1/25/2014 3:59 AM, Corinna Vinschen wrote: > On Jan 23 11:51, Corinna Vinschen wrote: >> On Jan 22 16:42, Chris O'Bryan wrote: On Mon, Jan 20, 2014 at 5:31 PM, Steven Penny wrote: > Are you certain the bug is present in Adam’s version? He > has tested it here > > http

Re: Telnet in latest Cygwin

2014-01-25 Thread Christopher Faylor
On Sat, Jan 25, 2014 at 04:15:17AM -0800, zeev wrote: >You can use the 'nc' (aka netcat) instead of telnet > >nc localhost 80 > >From a cygwin terminal it will give an equivalent result to 'telnet >localhost 80', and far better than Microsoft's #$&%#*%&$# telnet > >Search for 'nc' in the cygwin ins

Re: Telnet in latest Cygwin

2014-01-25 Thread zeev
You can use the 'nc' (aka netcat) instead of telnet nc localhost 80 >From a cygwin terminal it will give an equivalent result to 'telnet localhost 80', and far better than Microsoft's #$&%#*%&$# telnet Search for 'nc' in the cygwin installation. good luck -- View this message in context: h

Re: Maintainer for git?

2014-01-25 Thread Corinna Vinschen
On Jan 23 11:51, Corinna Vinschen wrote: > On Jan 22 16:42, Chris O'Bryan wrote: > > > On Mon, Jan 20, 2014 at 5:31 PM, Steven Penny wrote: > > > > > >> Are you certain the bug is present in Adam’s version? He has tested it > > >> here > > >> > > >> http://cygwin.com/ml/cygwin/2014-01/msg00085

[ANNOUNCEMENT] Updated: perl-Text-CSV_XS-1.03-1

2014-01-25 Thread David Stacey
Version 1.03-1 of perl-Text-CSV_XS has been uploaded. CHANGE LOG == 1.03- 2014-01-21, H.Merijn Brand * Update copyright to 2014 * Implement RCF7111 I suspect that there is a typo in the change log above, and that this release contains an implementation of RFC7111. See: http: