Re: cygwin64 has no LISP package
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 somewhere. Is there a way to use that hidden lisp interpreter, or to install the 32-bit clisp package in cygwin64? Without knowing what packages you're referring to, it's hard to be more specific but I believe that you'll find the packages that use LISP are doing so only through scripts that aren't crucial to the package operation. They are helper scripts, Emacs utilities, etc. There is, of course, no reason that these LISP scripts can't be run using the 32-bit version of LISP, as you've recognized, so this is your best recourse at the moment if you prefer to wait for a 64-bit version to be provided as part of distribution. Otherwise, you can always build a version for yourself while you wait for the official version. -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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
Re: SSHd configuration problems (System error 1376)
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: http://cygwin.1069669.n5.nabble.com/SSHd-configuration-problems-System-error-1376-tp113637p113919.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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
cygwin64 has no LISP package
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 hidden lisp interpreter, or to install the 32-bit clisp package in cygwin64? -- 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
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
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 ephemeral metadata in Windows could be quite a real file object in POSIX. -- WBR, Andrey Repin (anrdae...@yandex.ru) 28.12.2014, <06:34> Sorry for my terrible english... -- 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
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
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 FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
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 this is by design based on the documentation submitted > Corinna put together. Not a problem, although I'm curious as to why > it was setup this way. If you really curious, you can dig up the discussion on the subject starting about a year ago. I.e. a lengthy topic[1] in February of this year, when preliminary versions of this change became available. [1] mid:20140213143849.gh2...@calimero.vinschen.de -- WBR, Andrey Repin (anrdae...@yandex.ru) 28.12.2014, <03:59> Sorry for my terrible english... -- 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
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-003 (Christmas/New Year release)
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 as well. It would be nice if the names presented would be in what Microsoft calls the "NameSamCompatible" format instead of DOMAIN+USERNAME format. I see this is by design based on the documentation submitted Corinna put together. Not a problem, although I'm curious as to why it was setup this way. -- 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
Re: windows application manifest in gnu cpp application built on cygwin
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 and cannot find any html code or the word manifest. I would like to confirm the existence of a manifest and am looking for another tool that might work better. I presume I need mingw64-x86_64-windows-default-manifest-6.4-1 installed in the cygwin package manager. Is that correct? Is there documentation somewhere that describes the gnu c++ default manifest? I couldn't find anything with a search. LMH looks in windows-default-manifest package -- 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
Re: grep treating my text files as binary!
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 worked. > >I just keep a "CHCP 65001" at the beginning of all CMD files that are >meant to interface with Cygwin. Thank you for that. I had tried this earlier but CMD.EXE refused to run scripts when I had codepage 65001. Now it does, for some reason. -- 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
Re: grep treating my text files as binary!
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 "CHCP 65001" at the beginning of all CMD files that are meant to interface with Cygwin. -- Achim. (on the road :-) -- 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
Re: grep treating my text files as binary!
Warren Young wrote: >On Dec 25, 2014, at 11:41 AM, Thomas Wolff 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 automatically does the correct thing for all >members of the class text file without involving locales, or an >equivalent mechanism. ... >If grep runs into a byte sequence that makes it think it is not legal >for your current locale, it must treat the file as raw bytes, unless you >give it -a. > >If you dont like this behavior, say alias grep=grep -a in your >~/.bashrc, and forget the change ever happened. Itll be on you when >some non-text file gets treated as text and grep spams your terminal >with binary garbage, though. It's better to use the "alias grep='LC_ALL=C grep'" method. It keeps the old way of detecting binaries (for example it detects an .EXE as binary) while allowing you to match mostly-ASCII files with some mismatched-locale characters. The definition you ask for is already in the code. For us non-english people detecting what is "mostly ASCII" is mostly right, at least interactively. 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. -- 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
