From: Maxime Devos <maximedevos@telenet.be>
To: 46258@debbugs.gnu.org
Subject: bug#46258: openat, chownat, ... in Guile?
Date: Tue, 02 Feb 2021 15:45:31 +0100 [thread overview]
Message-ID: <6c9d1a78a198d4b5111fe42af67eaeb241e507ae.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Hi guilers,
I would like to see fchownat, openat, fchmodat
and any *at variants I forgot to appear in future versions
of Guile in some form. I have two proposals, which I will
illustrate with the procedure 'chmod':
* chmod can currently modify permissions of a file.
This OBJECT argument identifying the file can currently
be a filename or a port. Allow a ‘file in a directory’
object as well. This could be created with a procedure
(make-path-at DIRECTORY-PORT FILENAME)
This procedure does not perform any I/O, but rather
constructs what is effectively is a pair (DIRECTORY-PORT
. FILENAME) but with its own type.
* Follow the C API, but with Scheme types.
(chmodat DIRECTORY-PORT FILENAME MODE FLAGS)
where FLAGS can include AT_SYMLINK_NOFOLLOW (from chmod(2)
Linux man page)
Any thoughts?
Greetings,
Maxime
P.S. I'm not subscribed to bug-guile@gnu.org, please CC me.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
reply other threads:[~2021-02-02 14:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c9d1a78a198d4b5111fe42af67eaeb241e507ae.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=46258@debbugs.gnu.org \
/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.
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).