Further research shows that *all* commands (that I could think to try) return status 125 when called by emacs call-process via Tup. I'm assuming this has something to do with the fuse mount.
Does anyone know what status 125 means? I haven't determined whether it's coming from the processes themselves, or from emacs, or fuse. Also, is there any way that I can debug this while the mount is active? By the time Tup is finished, the paths reported by commands no longer exist. Thanks, Gavin -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
