RE: Editors set x-bit (sometimes)

2016-12-14 Thread Nellis, Kenneth
From: Achim Gratz > I said "-exec +", although I concur it was too easy to miss. Indeed, I overlooked the "+" and was unfamiliar with that option to find. Glad I asked. Learned something today. Thanx for the clarification. ☺ --Ken Nellis -- Problem reports: http://cygwin.com/problems.htm

Re: Editors set x-bit (sometimes)

2016-12-14 Thread Achim Gratz
Nellis, Kenneth writes: > Really? I always thought the opposite. With -exec, doesn't > find invoke the command for each single found object? While xargs > allows a single command to operate on a whole slew of objects. I said "-exec +", although I concur it was too easy to miss. > For example: >

Re: Editors set x-bit (sometimes)

2016-12-14 Thread Andrey Repin
Greetings, Nellis, Kenneth! >> From: Achim Gratz >> .. the latter is slightly less efficient and you have to >> do -print0/-0, but I tend to get it right more easily then the -exec >> stuff. > Really? I always thought the opposite. With -exec, doesn't > find invoke the command for each single fo

RE: Editors set x-bit (sometimes)

2016-12-14 Thread Nellis, Kenneth
> From: Achim Gratz > .. the latter is slightly less efficient and you have to > do -print0/-0, but I tend to get it right more easily then the -exec > stuff. Really? I always thought the opposite. With -exec, doesn't find invoke the command for each single found object? While xargs allows a sin

Re: Editors set x-bit (sometimes)

2016-12-13 Thread Henry S. Thompson
I find I can reproduce the OP's observations, and the most recent advice doesn't fix it (although it changes the symptoms): >From mintty/bash: 639> cd /tmp 641> ls -ld . drwxrwxr-x+ 1 ht None 0 Dec 13 19:55 ./ 640> getfacl . # file: . # owner: ht # group: None user::rwx group::r

Re: Editors set x-bit (sometimes)

2016-12-13 Thread Achim Gratz
Brian Inglis writes: > Remove DACLs Default ACLs also on directories using: > setfacl -bk ~/.[!.]* ~/.[!.]*/**/ ~/.[!.]*/**/* \ > /???/**/ /???/**/* /sbin/ /sbin/* > - that takes a while to run, and you may get a few anonymous > setfacl: Permission denied > messag

Re: Editors set x-bit (sometimes)

2016-12-13 Thread Brian Inglis
On 2016-12-13 08:20, Ronald Otto Valentin Fischer wrote: >On 2016-12-13 10:57, Ken Brown wrote: >> Does this help? >> https://cygwin.com/faq/faq.html#faq.using.same-with-permissions > While interesting, it seems to describe a different phenomenon. > Actually, when I create files by Cygwin tool

Re: Editors set x-bit (sometimes)

2016-12-13 Thread Ronald Otto Valentin Fischer
> Does this help? > > https://cygwin.com/faq/faq.html#faq.using.same-with-permissions While interesting, it seems to describe a different phenomenon. Actually, when I create files by Cygwin tools only (touch, nano, ), the access rights are always correct. Indeed, even after removing the

Re: Editors set x-bit (sometimes)

2016-12-13 Thread Ken Brown
On 12/13/2016 5:39 AM, Ronald Fischer wrote: Does anybody have an explanation for the following strange phenomenon? When I create Ruby files (*.rb) with an, the files end up with the x-bit set with some editors, while this does not happen with some other editors. This is annoying, because when I

Editors set x-bit (sometimes)

2016-12-13 Thread Ronald Fischer
Does anybody have an explanation for the following strange phenomenon? When I create Ruby files (*.rb) with an, the files end up with the x-bit set with some editors, while this does not happen with some other editors. This is annoying, because when I use git to put the file in a repository, and t