Re: grep treating my text files as binary!

2014-12-27 Thread Bengt Larsson
Warren Young wrote: On Dec 25, 2014, at 11:41 AM, Thomas Wolff t...@towo.net wrote: In any case the argument is quite artificial since the new behaviour hits many files that are in fact text files. Please define the term “text file” in a way that allows a C programmer to write a program that

Re: grep treating my text files as binary!

2014-12-27 Thread Achim Gratz
Am 27.12.2014 um 11:07 schrieb Bengt Larsson: I ran into this, actually. I keep a list of my directories and it is in CP1252 for reasons of interfacing with CMD.EXE. Suddenly grep couldn't match it. But I figured something was up and set my locale to CP1252 and then it worked. I just keep a

Re: grep treating my text files as binary!

2014-12-27 Thread Bengt Larsson
Achim Gratz wrote: Am 27.12.2014 um 11:07 schrieb Bengt Larsson: I ran into this, actually. I keep a list of my directories and it is in CP1252 for reasons of interfacing with CMD.EXE. Suddenly grep couldn't match it. But I figured something was up and set my locale to CP1252 and then it

Re: windows application manifest in gnu cpp application built on cygwin

2014-12-27 Thread Marco Atzeri
On 12/26/2014 11:09 PM, LMH wrote: Andrey Repin wrote: Greetings, LMH! Thanks for the reply, I tried to use ManifestView to look at the manifest, but ManifestVeiw can't seem to find a manifest to display. I'm not sure why that would be. I have also looked at the binary with a text editor

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)

2014-12-27 Thread Bryan Berns
Finally had a chance to test out the new release, albeit in a very limited fashion. On our multi-domain forest with SID-History enabled, running 'ls -l' was able to lookup account names for groups and users on files. Some ACEs had SIDs that would only be in present SID-History and those worked

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)

2014-12-27 Thread Andrey Repin
Greetings, Bryan Berns! It would be nice if the names presented would be in what Microsoft calls the NameSamCompatible format instead of DOMAIN+USERNAME If you mean DOMAIN\USER scheme, it would not work for obvious reasons. I.e., you can't have a file name with [back]slash. format. I see

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)

2014-12-27 Thread Bryan Berns
Thanks for the reply, Andrey. I'll take a look at the archives for February. I'm not sure how it'd be obvious given that's it's just descriptive metadata for the SID, but I'll try to educate myself before rehashing a previous discussion. -- Problem reports: http://cygwin.com/problems.html

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)

2014-12-27 Thread Andrey Repin
Greetings, Bryan Berns! I'll take a look at the archives for February. I'm not sure how it'd be obvious given that's it's just descriptive metadata for the SID, but I'll try to educate myself before rehashing a previous discussion. This is where POSIX is different from Windows. What is

cygwin64 has no LISP package

2014-12-27 Thread Phil _
cygwin64 has no package with any version of LISP. I install cygwin largely to use LISP, and have to keep both cygwin32 and cygwin64 installations just for clisp, which is in cygwin32. Some of the available packages use LISP, so there must be a LISP in there somewhere. Is there a way to use that

Re: SSHd configuration problems (System error 1376)

2014-12-27 Thread craigmcd
I had the same issue on Windows 2003 32-bit. Without the -w option, the only name returned is root, not Administrators: I had to hack /usr/share/csih/cygwin-service-installation-helper.sh in a couple of places to finally make it work. -- View this message in context:

Re: cygwin64 has no LISP package

2014-12-27 Thread Larry Hall (Cygwin)
On 12/27/2014 11:38 PM, Phil _ wrote: cygwin64 has no package with any version of LISP. I install cygwin largely to use LISP, and have to keep both cygwin32 and cygwin64 installations just for clisp, which is in cygwin32. Some of the available packages use LISP, so there must be a LISP in there