> I can see that an empty file has been constructed: > > #################################### > fermi ~/work/whalesong $ ls -l hi > -r-xr-xr-x 1 dyoo nogroup 0 Jun 14 15:49 hi* > #################################### > > At the very least, the executable bit is set. I'm about to start > looking through the source to launcher/launcher to figure out what's > going on, but want to double check: am I misusing the library?
Bug tracked! There's a missing condition that needs to be added: the launcher library assumes that the template file is writable, because it uses copy-file to move it into the destination. However, on my setup here in the Brown CS lab, the Racket installation is shared, and none of the collection files are user-writable. So the template-writing function must use file-or-directory-permissions. I was about to write a patch, but encountered what looks like a bug to me. I've been staring at the bit patterns for read,write,execute in: http://docs.racket-lang.org/reference/Filesystem.html#(def._((lib._racket/file..rkt)._user-read-bit)) Is it just me, or are the bits for read and execute backwards? _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
