unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: doc stat:dev, stat:mode
Date: Mon, 08 Sep 2003 09:56:29 +1000	[thread overview]
Message-ID: <87ad9grw42.fsf@zip.com.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 103 bytes --]

        * posix.texi (File System): In stat:dev and stat:mode, clarify that
        both are numbers.


[-- Attachment #2: posix.texi.stat-numbers.diff --]
[-- Type: text/plain, Size: 1088 bytes --]

--- posix.texi.~1.25.~	1970-01-01 10:00:01.000000000 +1000
+++ posix.texi	2003-09-07 11:47:17.000000000 +1000
@@ -577,15 +577,15 @@
 integers:
 
 @deffn {Scheme Procedure} stat:dev st
-The device containing the file.
+The device number containing the file.
 @end deffn
 @deffn {Scheme Procedure} stat:ino st
 The file serial number, which distinguishes this file from all
 other files on the same device.
 @end deffn
 @deffn {Scheme Procedure} stat:mode st
-The mode of the file.  This includes file type information and
-the file permission bits.  See @code{stat:type} and
+The mode of the file.  This is an integer which incorporates file type
+information and file permission bits.  See also @code{stat:type} and
 @code{stat:perms} below.
 @end deffn
 @deffn {Scheme Procedure} stat:nlink st
@@ -626,7 +626,7 @@
 @end deffn
 
 In addition, the following procedures return the information
-from stat:mode in a more convenient form:
+from @code{stat:mode} in a more convenient form:
 
 @deffn {Scheme Procedure} stat:type st
 A symbol representing the type of file.  Possible values are

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

                 reply	other threads:[~2003-09-07 23:56 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=87ad9grw42.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).