On Mar 30, 5:56 pm, Tony Mechelynck wrote: > On 30/03/13 20:46, AndyHancock wrote: FAT filesystems have no > built-in executable bit. I'm less sure about NTFS filesystems. OTOH > POSIX-compatible filesystems typically have "rwxrwxrwx" permissions, > and IIRC Cygwin tries to simulate that for your Windows files. When > I was on Windows (with Cygwin installed), ISTR that everything had > the executable bits set from the Cygwin POV. Windows executables are > of course distinguished by their extension (.EXE etc. for binaries, > .BAT etc. for shell scripts) but you may also have bash scripts with > either .sh or no extension at all, for use with Cygwin bash. > > You may try running chmod a+x * to mark everything as "executable", > which will make the *distinction* disappear (everything will be the > same again). GNU chmod has a -R (recursive) option but I'm not sure > how to avoid looping forever on Cygwin's representation of your > Windows filesystem. Maybe reading "man chmod" in a Cygwin bash shell > may help you.
Thanks, Tony. I'm on Windows 7, so it's NTFS. I just double checked, and whether a file is marked executable according to "ls -l" in cygwin's bash seems to vary, though I'm not sure how cygwin decides. "chmod -R" will fix it for the moment, but the directory subtree that I intend to use netrw on typically varies alot, so it's be great if I there is a way for netrw to ignore executability. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
