From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Subject: file-exists? confused
Date: Mon, 13 Mar 2006 08:55:49 -0800 [thread overview]
Message-ID: <20060313165454.M814@ccrma.Stanford.EDU> (raw)
The new Guile's file-exists? function is confused by very large files:
guile> (version)
"1.8.0"
guile> (file-exists? "/home/bil/zap/sounds/bigger.snd")
#f
guile> (quit)
/home/bil/ ls -la /home/bil/zap/sounds/bigger.snd
-rw-r--r-- 1 bil bil 6350320648 Mar 13 04:07 /home/bil/zap/sounds/bigger.snd
guile> (version)
"1.6.4"
guile> (file-exists? "/home/bil/zap/sounds/bigger.snd")
#t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-03-13 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 16:55 Bill Schottstaedt [this message]
2006-03-13 21:17 ` file-exists? confused Kevin Ryde
2006-03-14 22:33 ` Kevin Ryde
2006-03-25 22:48 ` Marius Vollmer
2006-03-29 0:45 ` Kevin Ryde
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=20060313165454.M814@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
/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).