From: Andy Wingo <wingo@pobox.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-devel@gnu.org
Subject: Re: Some non-standard O_* flags are missing
Date: Tue, 09 Mar 2021 21:36:25 +0100 [thread overview]
Message-ID: <87mtvc2hfa.fsf@pobox.com> (raw)
In-Reply-To: <eee99a01c43dec23cd119f71b9a9758c7986aceb.camel@telenet.be> (Maxime Devos's message of "Sun, 31 Jan 2021 22:13:10 +0100")
Hi :) Sure, would be happy to accept a patch for these. It's adding
more definitions to the base environment, which is usually a negative,
but we'll have to find some kind of module solution for all of these
flags at some point. If you do send a patch, please update the manual
and NEWS also.
Cheers,
Andy
On Sun 31 Jan 2021 22:13, Maxime Devos <maximedevos@telenet.be> writes:
> Hi guilers,
>
> I noticed the following open flags are not defined:
> O_NOFOLLOW, O_TMPFILE, O_IGNORE_CTTY, O_NOLINK,
> O_SHLOCK, O_EXLOCK, O_ASYNC, O_NOATIME.
>
> Some of these are Hurd-specific, Linux-specific
> and BSD-specific. I'm particularily interested
> in O_NOFOLLOW, O_TMPFILE, O_IGNORE_CTTY, O_NOLINK
> and O_NOATIME, the others don't matter for me,
> though they may be useful for others.
>
> Could extra O_* flags be exported to Guile (in libguile/filesys.c)
> on systems where they are defined?
>
> Greetings,
> Maxime
next prev parent reply other threads:[~2021-03-09 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 21:13 Some non-standard O_* flags are missing Maxime Devos
2021-03-09 20:36 ` Andy Wingo [this message]
2021-03-09 21:47 ` Maxime Devos
2021-03-10 20:08 ` Andy Wingo
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=87mtvc2hfa.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).