> chmod in cygwin is not working. I did the following:
>
> mkdir mybin
> gvim mybin/vi
> ... /* mybin vi just does a gvim */
> chmod +x mybin/vi
> -rw-r---r-- 1 default unknown 9 jun 18 13:11
>
> (There is a mybin/vi at the end but in this message
> it wouldn't fit on
> not sure if it a actual bug or not, but chmod reports incorrectly when
> it tries to modify file permissions on file systems it cannot handle,
> e.g. vfat. The --verbose switch reports that the switch is successful,
> but a quick ls -l of the file in question shows that the permissions are
> not
hello,
not sure if it a actual bug or not, but chmod reports incorrectly when
it tries to modify file permissions on file systems it cannot handle,
e.g. vfat. The --verbose switch reports that the switch is successful,
but a quick ls -l of the file in question shows that the permissions are
not c
chmod in cygwin is not working. I did the following:
mkdir mybin
gvim mybin/vi
... /* mybin vi just does a gvim */
chmod +x mybin/vi
-rw-r---r-- 1 default unknown 9 jun 18 13:11
(There is a mybin/vi at the end but in this message
it wouldn't fit on the line).
Also, n
iI did du -sb and got:
-828863916
--
Karel 'Clock' Kulhavy
___
Bug-fileutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-fileutils
Bob --
...and then Bob Proulx said...
%
% > % long as the program's --help output is kept up to date with the
% > % program's options then the man page automatically tracks. Therefore
% >
% > So -P needs a bit more explanation ;-)
%
% Submit a documentation patch! :-)
I might, since you ask
