all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: drew.adams@oracle.com
Cc: 21346-done@debbugs.gnu.org
Subject: bug#21346: 25.0.50; REGRESSION: `directory-files' raises error for DIR that	is	`file-accessible-directory-p'
Date: Mon, 31 Aug 2015 18:01:36 +0300	[thread overview]
Message-ID: <838u8r1oz3.fsf@gnu.org> (raw)
In-Reply-To: <83lhcy59xp.fsf@gnu.org>

> Date: Wed, 26 Aug 2015 18:46:58 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 21346@debbugs.gnu.org
> 
> > > > That predicate would seem to be unusable as a general test for
> > > > access to a directory.  IOW, what it claims it does is hardly
> > > > what it does, apparently.
> > > 
> > > It's not unusable.  It checks the read-only bit (and the executable
> > > bit for files).
> > 
> > Unusable "as a general test for access".
> 
> I disagree.  It does test that the file exists and is a directory, so
> it _will_ tell you when either of these 2 conditions is false.  It
> just can yield a false positive regarding the success of opening and
> reading the directory.  The alternative is to complicate the heck out
> of the implementation, make it much slower, and get false negatives
> instead.  I think the alternative is worse.

On further thought, I found a simple and surprisingly efficient method
of testing directory accessibility without any false positives, and
made the corresponding changes.

> > > > And given this "inconsistency", don't you think this gotcha should
> > > > be mentioned in the doc - of `file-accessible-directory-p', for
> > > > example?
> > > 
> > > Maybe.  I'll have to think of a useful way of describing this.
> > 
> > Perhaps what you said above, if nothing more informative can be found:
> > 
> >   On Windows, that test is not reliable enough.
> 
> Done.

I've now removed that caveat from the doc string.





  reply	other threads:[~2015-08-31 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<2974d023-5059-414f-960d-273fbeaca5de@default>
     [not found] ` <<83fv37fdcg.fsf@gnu.org>
2015-08-25 18:34   ` bug#21346: 25.0.50; REGRESSION: `directory-files' raises error for DIR that is `file-accessible-directory-p' Drew Adams
2015-08-25 19:09     ` Eli Zaretskii
     [not found]   ` <<bb9288b5-fa49-41eb-a016-3798404985aa@default>
     [not found]     ` <<83egirfane.fsf@gnu.org>
2015-08-25 20:55       ` Drew Adams
2015-08-26 15:46         ` Eli Zaretskii
2015-08-31 15:01           ` Eli Zaretskii [this message]
     [not found]       ` <<b9a02743-e606-432e-bed0-8de4121098b9@default>
     [not found]         ` <<83lhcy59xp.fsf@gnu.org>
2015-08-26 16:27           ` Drew Adams
     [not found]           ` <<838u8r1oz3.fsf@gnu.org>
2015-08-31 15:05             ` Drew Adams
2015-08-25 17:48 Drew Adams
2015-08-25 18:10 ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838u8r1oz3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21346-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.