|
From: | A. Peter Blicher |
Subject: | bug#41570: 26.3; dired chown |
Date: | Thu, 28 May 2020 08:54:29 -0700 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 |
The main reason I have more use for chown in windows compared to when I was using Unix is that Windows creates a profusion of different ownerships even for files I create under a single user (depending on how they were created), resulting in a mess that I often need to clean up. That mess is most evident using Dired, because it shows ownership by default, while usually Windows hides that information.
The requirement for elevated privilege is not an issue for me, because I run in that mode all the time, against all advice, mainly because Windows' permission handling is so screwed up and opaque. However, for those who don't, that might either require extra code to handle, or maybe Windows would raise an elevation prompt dialog, not sure.
Thanks for considering it. --peter On 5/27/2020 11:44 PM, Eli Zaretskii wrote:
From: "A. Peter Blicher" <blicher@comcast.net> Date: Wed, 27 May 2020 14:46:39 -0700 Dired chown command complains that chown is not available for windows systems. However, windows versions >= 7 (at least) have the "takeown" command, which while not as comprehensive as the unix chown command at least allows the current user to take ownership of a file/dir, as long as the user has admin privileges. It would be useful for dired to permit this possibility on windows systems.AFAIU, 'takeown' is different from 'chown', in that it only allows to change the file's owner to either the current user or the Administrators group, it doesn't allow you to change the ownership to any other user except one of those two. Also, I think the command requires elevation, doesn't it (thus you mention "admin privileges")? So I'm not sure that command is a good replacement for 'chown', but maybe you have something in mind I'm missing? Thanks.
[Prev in Thread] | Current Thread | [Next in Thread] |