two questions on file modes
Shiro Kawai
(24 Jul 2020 20:15 UTC)
|
Re: two questions on file modes
hga@xxxxxx
(24 Jul 2020 21:16 UTC)
|
Re: two questions on file modes
Shiro Kawai
(24 Jul 2020 21:48 UTC)
|
Re: two questions on file modes
Lassi Kortela
(26 Jul 2020 19:24 UTC)
|
Re: two questions on file modes
Lassi Kortela
(26 Jul 2020 19:39 UTC)
|
Re: two questions on file modes hga@xxxxxx (26 Jul 2020 20:18 UTC)
|
Re: two questions on file modes
Lassi Kortela
(26 Jul 2020 20:33 UTC)
|
Re: two questions on file modes
John Cowan
(26 Jul 2020 23:15 UTC)
|
Re: two questions on file modes
Lassi Kortela
(27 Jul 2020 06:09 UTC)
|
Re: two questions on file modes
John Cowan
(28 Jul 2020 20:31 UTC)
|
The argument of Pareto 80/20 principle lowering the effort to implement SRFI 170 remains strong for adding port/fdes to these procedures. Can you make a case that this is really useful, when every extra bit of effort adds up? The same is a strong argument for combining setting file and group ownership in one procedure, but I remain uncomfortable with keeping the name set-file-*owner*, although not by a great deal, seeing as how chown(1) works that way. Or at least I frequently use that feature.... #f for no change strikes me as excellent. - Harold ----- Original message ----- From: Lassi Kortela <xxxxxx@lassi.io> Date: Sunday, July 26, 2020 2:39 PM Since POSIX is the main inspiration for this SRFI, how about: (set-file-mode fname/port/fdes mode-bits) * fname - chmod() * port/fdes - fchmod() (set-file-owner fname/port/fdes uid gid) * fname - chown() * port-fdes - fchown() uid and/or gid can be #f for no change