On Wed, Dec 21, 2005 at 12:53:29PM -0700, Don Peterson wrote:
>PS: I'd like to thank the cygwin developers and the Red Hat executives
>(past and present) who continue to support cygwin. Life on Windows
>would be miserable without your work and dedication.
I appreciate your appreciation but, just
On Wed, 21 Dec 2005, Don Peterson wrote:
> Please reference the mail list thread
> http://sourceware.org/ml/cygwin/2005-10/msg00921.html for what I could
> find on this topic. I didn't find an answer, but I have a suspicion
> that the problem's cause is not due to cygwin's behavior. Output of
>
Hannu E K Nevalainen wrote:
> find -print0 | xargs -null
Correction, the above should of course read:
find -print0 | xargs --null
/H
--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwi
Don Peterson wrote:
> I use the following shell function as a quick hack to recursively fix
> things:
>
> unx ()
> {
> find . -type d | xargs chmod a+x;
> find . -type f ! -name "*.exe" | xargs chmod a-x }
>
> Its problem is that it doesn't work on file names with space
> characters (on
Don Peterson wrote:
> Problem statement: running a non-cygwin program in a console generate
> files with the execute bit set, even if your umask doesn't allow it.
Why would a non-cygwin process have any concept of 'umask', let alone
respect its setting? This is entirely a Cygwin mechanism.
Thi
5 matches
Mail list logo
