Summary

file-read-access? returns #f for non-existent files

Metadata

Attachments

Description

As seen on IRC:

> <Seylerius> Hrm. Isn't `file-read-access?` supposed to error out on a nonexistent file?

Expected outcome:

 (file-read-access? "/con/con") ;=> <file error>

Actual outcome:

 (file-read-access? "/con/con") ;=> #f

I've worked out a patch with the help of TheLemonMan on IRC.

Changes and comments

[2017-07-07 22:47:36 UTC] wasamasa attached 0001-Handle-other-errors-than-EACCES-for-access-3.patch (description=#f)

[2017-07-14 17:42:50 UTC] felix wrote:

The patch and the intended behaviour looks correct. But this would be a Change Request, I suppose.

[2017-10-14 17:01:36 UTC] wasamasa changed milestone from someday to 5.0

[2017-10-14 17:01:36 UTC] wasamasa wrote:

I've changed my mind and reworked the patch for C5.

[2017-10-14 17:01:52 UTC] wasamasa attached 0001-Handle-other-errors-than-EACCES-for-access-3.2.patch (description=#f)

[2017-10-20 11:33:25 UTC] sjamaan changed status from new to closed

[2017-10-20 11:33:25 UTC] sjamaan set resolution to fixed

[2017-10-20 11:33:25 UTC] sjamaan wrote:

Fixed by 536e2351cf5836e76df79395813501fcb2c4b034