Re: test -r or -x always return false on an NFS mount?

2020-10-14 Thread Corinna Vinschen
On Oct 13 21:00, Mario Emmenlauer wrote: > Hi Corinna, great to have you back :-) Thanks! > On 13.10.20 20:36, Corinna Vinschen wrote: > > > > > Everything seems to work quite well, and in `ls -la` I can see the > > > > > file permissions and user and group entries. But when using `test` > > > >

Re: test -r or -x always return false on an NFS mount?

2020-10-14 Thread Mario Emmenlauer
On 14.10.20 10:28, Corinna Vinschen wrote: On Oct 13 21:00, Mario Emmenlauer wrote: On 13.10.20 20:36, Corinna Vinschen wrote: Everything seems to work quite well, and in `ls -la` I can see the file permissions and user and group entries. But when using `test` to check for read (`test -r`) or e

Re: test -r or -x always return false on an NFS mount?

2020-10-14 Thread Corinna Vinschen
On Oct 14 11:06, Mario Emmenlauer wrote: > On 14.10.20 10:28, Corinna Vinschen wrote: > > Actually, not really. It's weird in fact, given ls(1) shows the > > desired result. That would point to a bug in access(2), but there's > > no special code in access(2) for NFS. For filesystems not supporti

Strange behaviour with winsymlinks:native

2020-10-14 Thread David Allsopp via Cygwin
I've been doing some working around the problems with Cygwin 3.1.5+ WSL junction points in Docker and found three unexpected pieces of behaviour with CYGWIN=winsymlinks:native In all cases, these work as expected with the default symlink behaviour (i.e. CYGWIN unset or without a winsymlinks option

Re: test -r or -x always return false on an NFS mount?

2020-10-14 Thread Mario Emmenlauer
On 14.10.20 13:50, Corinna Vinschen wrote: > On Oct 14 11:06, Mario Emmenlauer wrote: >> On 14.10.20 10:28, Corinna Vinschen wrote: >>> Actually, not really. It's weird in fact, given ls(1) shows the >>> desired result. That would point to a bug in access(2), but there's >>> no special code in ac

Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

2020-10-14 Thread Jérôme Froissart
Thank you everyone, I now have a better understanding of how Windows and Cygwin work (being rather a Linux guy, I was not really aware of all of this). However, there is still a question that is puzzling me. I now understand _why_ things happen that way, but I am still wondering whether this is re

Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments

2020-10-14 Thread Jérôme Froissart
Le mer. 14 oct. 2020 à 23:47, Jérôme Froissart a écrit : > However, there is still a question that is puzzling me. I now > understand _why_ things happen that way, but I am still wondering > whether this is really what we _want_. I mean, keeping the double > quotes around an UTF-8 argument just be

Re: UTF-8 quoted args passed to program include quotes when run from cmd

2020-10-14 Thread Brian Inglis
[changed subject] On 2020-10-14 15:47, Jérôme Froissart wrote: >> (As evidence of this: the Cygwin command line parser was able to break the >> command line into arguments correctly, but chose to retain the double >> quotes.) >> >> #include >> >> int main(int argc, char *argv[]) >> {