From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: file-exists? using stat
Date: Tue, 16 Sep 2003 06:41:55 +1000 [thread overview]
Message-ID: <87ad95238s.fsf@zip.com.au> (raw)
In-Reply-To: <3F62B283.40508@dirk-herrmanns-seiten.de> (Dirk Herrmann's message of "Sat, 13 Sep 2003 08:00:35 +0200")
Dirk Herrmann <dirk@dirk-herrmanns-seiten.de> writes:
>
> + ;; Make sure to follow the effective UID/GID not the real ID, as it is
> + ;; done by stat. file-exists? will normally be used as a prelude to
> + ;; opening or some other operation, and it's the effective ID
> which will
> + ;; apply there.
I guess I see access? as being just plain wrong, and that the gory
details concerning this are best covered in the manual (see other
message), since it's a general matter, applying to lots of places one
might think of using it.
I'll add to the code the note about what emacs does though.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-09-15 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 23:00 file-exists? using stat Kevin Ryde
2003-09-12 19:04 ` Rob Browning
2003-09-13 6:00 ` Dirk Herrmann
2003-09-15 20:41 ` Kevin Ryde [this message]
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=87ad95238s.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).