From: Michael Albinus <michael.albinus@gmx.de>
To: Romain Francoise <romain@orebokech.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH v2] POSIX ACL support
Date: Fri, 07 Dec 2012 09:19:09 +0100 [thread overview]
Message-ID: <87d2ym1dhe.fsf@gmx.de> (raw)
In-Reply-To: <87zk1rm0b9.fsf@silenus.orebokech.com> (Romain Francoise's message of "Thu, 06 Dec 2012 20:45:46 +0100")
Romain Francoise <romain@orebokech.com> writes:
> Hi Eli,
Hi,
>>> +DEFUN ("file-acl", Ffile_acl, Sfile_acl, 1, 1, 0,
>>> + doc: /* Return ACL entries of file named FILENAME, as a string.
>>> +Return nil if file does not exist or is not accessible, or if Emacs was
>>> +not compiled with ACL support. */)
>
>> The last sentence of the doc string is inaccurate, because remote
>> files are supported even if Emacs was not built with ACL support.
>
> Yes... if there's an implementation of file-acl for the remote handler.
> This bit was inherited from the SELinux functions, which have a similar
> docstring. I'm not sure how to phrase it better, though.
| Return nil if file does not exist or is not accessible, or if Emacs is
| not able to determine the ACL entries. The latter happens, if Emacs was
| not compiled with ACL support, or a remote file handler returns nil
| ACL entries. */)
Similar wording could be applied to file-selinux-context and
set-file-selinux-context.
Once the patch is installed in the trunk (i.e., the interface is
stabilized), I will try to implement corresponding file name handlers.
> Thanks!
Best regards, Michael.
next prev parent reply other threads:[~2012-12-07 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 20:04 [PATCH v2] POSIX ACL support Romain Francoise
2012-12-04 20:42 ` Eli Zaretskii
2012-12-06 19:45 ` Romain Francoise
2012-12-07 8:19 ` Michael Albinus [this message]
2012-12-07 9:32 ` Eli Zaretskii
2012-12-05 2:28 ` Glenn Morris
2012-12-05 3:53 ` Eli Zaretskii
2012-12-05 4:09 ` Glenn Morris
2012-12-05 16:16 ` Eli Zaretskii
2012-12-05 17:18 ` Glenn Morris
2012-12-06 19:48 ` Romain Francoise
2012-12-06 21:33 ` Stefan Monnier
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=87d2ym1dhe.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
/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).