From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: michael.albinus@gmx.de, 13226@debbugs.gnu.org
Subject: bug#13226: 24.3.50; set-file-acl on MS Windows shall check ACL string format
Date: Wed, 19 Dec 2012 18:33:22 +0200 [thread overview]
Message-ID: <83txringrx.fsf@gnu.org> (raw)
In-Reply-To: <jwva9tap15k.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Wed, 19 Dec 2012 09:32:36 -0500
> Cc: 13226@debbugs.gnu.org
>
> > (file-acl "~/.emacs")
>
> > "O:S-1-5-21-3955186872-1115707380-970145838-1000G:S-1-5-21-3955186872-1115707380-970145838-513D:(A;;FA;;;SY)(A;;FA;;;BA)(A;;FA;;;S-1-5-21-3955186872-1115707380-970145838-1000)"
>
> This looks thoroughly unportable.
It is explicitly documented as platform-specific in the ELisp manual.
Once again, the original design had a modest goal: allow to copy these
attributes from file to file. Are you sure we want to extend that to
a much more complex system which would allow a Lisp program to
interpret those strings in a platform-independent manner?
> We should probably change file-acl so that its return value is tagged
> with the "acl-system" it uses. It could be a prefix like "w32:".
As I wrote elsewhere, I don't see the rationale.
> Then we can change set-file-acl so that it can either try to perform
> conversion or signal a proper error that copy-file can handle.
copy-file the primitive is not affected, it already does TRT with this
scenario. copy-file handler for remote files should simply catch and
ignore the errors, like the primitive does.
next prev parent reply other threads:[~2012-12-19 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 12:24 bug#13226: 24.3.50; set-file-acl on MS Windows shall check ACL string format Michael Albinus
2012-12-19 14:32 ` Stefan Monnier
2012-12-19 14:38 ` Michael Albinus
2012-12-19 16:25 ` Eli Zaretskii
2012-12-19 16:33 ` Eli Zaretskii [this message]
2012-12-19 14:34 ` Stefan Monnier
2012-12-19 14:59 ` Michael Albinus
2012-12-19 15:46 ` Romain Francoise
2012-12-19 15:57 ` Michael Albinus
2012-12-19 16:29 ` Eli Zaretskii
2012-12-19 16:42 ` Romain Francoise
2012-12-19 16:56 ` Eli Zaretskii
2012-12-19 17:44 ` Michael Albinus
2012-12-19 18:36 ` Stefan Monnier
2012-12-19 21:18 ` Eli Zaretskii
2012-12-20 0:53 ` Stefan Monnier
2012-12-22 14:19 ` Eli Zaretskii
2013-01-04 13:20 ` Michael Albinus
2012-12-19 16:23 ` Eli Zaretskii
2012-12-19 16:55 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83txringrx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13226@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@IRO.UMontreal.CA \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).